public interface NonBlockingMessageProcessor extends MessageProcessor, NonBlockingSupported
NonBlockingMessageProcessor differs from other message processors in that it supports
both blocking and non-blocking processing.
MuleEvent is not synchronous and a MessageExchangePattern that
expects a response then the implementations of this message processor should return an instance of
NonBlockingVoidMuleEvent and invoke the events ReplyToHandler when
a response is available or an exception errors.
MuleEvent is synchronous, then the response should be returned and the
ReplyToHandler not used.processCopyright © 2003–2015 MuleSoft, Inc.. All rights reserved.