public interface Conduit extends Observable
A Conduit channels messages to a single destination, though this destination may fan-out to multiple receivers (for example a JMS topic).
A Conduit may have a back-channel, on which transport-level responses are received. Alternatively the back-channel destination may be decoupled, in which case the response it is received via a separate Conduit. The crucial distinction is whether the Conduit can itself correlate the response (which may be synchronous, or may be delivered via a dedicated destination).
Conduits may be used for multiple messages, either serially or concurrently, with the implementation taking care of mapping onto multiple transport resources (e.g. connections) if neccessary to support concurrency.
Binding-level MEPs may be realized over one or more Conduits.
| Modifier and Type | Method and Description |
|---|---|
void |
close()
Close the conduit
|
void |
close(Message message)
Close the connections associated with the message
|
EndpointReferenceType |
getTarget() |
void |
prepare(Message message)
Prepare the message for sending.
|
getMessageObserver, setMessageObservervoid prepare(Message message) throws IOException
message - the message to be sent.IOExceptionvoid close(Message message) throws IOException
IOExceptionEndpointReferenceType getTarget()
void close()
Apache CXF