| java.lang.Object org.mule.transport.AbstractConnectable org.mule.transport.AbstractMessageDispatcher
All known Subclasses: org.mule.transport.ftp.FtpMessageDispatcher, org.mule.transport.udp.UdpMessageDispatcher, org.mule.transport.stdio.StdioMessageDispatcher, org.mule.transport.http.HttpClientMessageDispatcher, org.mule.transport.tcp.TcpMessageDispatcher, org.mule.transport.soap.axis.AxisMessageDispatcher, org.mule.transport.UnsupportedMessageDispatcher, org.mule.transport.jdbc.JdbcMessageDispatcher, org.mule.transport.quartz.QuartzMessageDispatcher, org.mule.transport.xmpp.XmppMessageDispatcher, org.mule.transport.email.SmtpMessageDispatcher, org.mule.transport.bpm.ProcessMessageDispatcher, org.mule.transport.vm.VMMessageDispatcher, org.mule.transport.cxf.CxfMessageDispatcher, org.mule.transport.rmi.RmiMessageDispatcher, org.mule.transport.jms.JmsMessageDispatcher, org.mule.transport.file.FileMessageDispatcher,
AbstractMessageDispatcher | abstract public class AbstractMessageDispatcher extends AbstractConnectable implements MessageDispatcher(Code) | | Provide a default dispatch (client) support for handling threads lifecycle and validation.
|
isTransactionRollback | protected boolean isTransactionRollback()(Code) | | Checks to see if the current transaction has been rolled back
|
useRemoteSync | protected boolean useRemoteSync(MuleEvent event)(Code) | | RemoteSync causes the message dispatch to wait for a response to an event on a
response channel after it sends the event. The following rules apply to
RemoteSync 1. The connector has to support remoteSync. Some transports do not
have the notion of a response channel 2. Check if the endpoint has been
configured for remoteSync 3. Check if the REMOTE_SYNC message header has been
set 4. Finally, if the current service has a response router configured,
that the router will handle the response channel event and we should not try
and receive a response in the Message dispatcher If remotesync should not be
used we must remove the REMOTE_SYNC header Note the MuleClient will
automatically set the REMOTE_SYNC header when client.send(..) is called so
that results are returned from remote invocations too.
Parameters: event - the current event true if a response channel should be used to get a resposne from theevent dispatch. |
|
|