org.mule.processor

Interface NonBlockingMessageProcessor

All Superinterfaces:

MessageProcessor, NonBlockingSupported

All Known Subinterfaces:

OutboundEndpoint

All Known Implementing Classes:

AbstractMessageProcessorChain, AbstractNonBlockingMessageProcessor, ChoiceRouter, DefaultHttpRequester, DefaultMessageProcessorChain, DefaultOutboundEndpoint, DynamicOutboundEndpoint, DynamicURIOutboundEndpoint, InterceptingChainLifecycleWrapper, MessageEnricher, SimpleMessageProcessorChain, SubflowInterceptingChainLifecycleWrapper, WSConsumer

public interface NonBlockingMessageProcessor
extends MessageProcessor, NonBlockingSupported

A NonBlockingMessageProcessor differs from other message processors in that it supports both blocking and non-blocking processing.
If the current 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.
Alternatively if the MuleEvent is synchronous, then the response should be returned and the ReplyToHandler not used.

Since:

3.7

Method Summary

Methods inherited from interface org.mule.api.processor.MessageProcessor

process