org.mule.api.source

Interface NonBlockingMessageSource

All Superinterfaces:

MessageSource

public interface NonBlockingMessageSource
extends MessageSource

NonBlockingMessageSource's create instances of MuleEvent that contain a ReplyToHandler allowing for a response or error to be returned asynchronously by a different thread freeing up the request thread.

Implementations must support both blocking and non-blocking and therefore need to test the response MuleEvent returned when invoking MessageProcessor.process(org.mule.api.MuleEvent) on the listener. If the event returned is an instance of NonBlockingVoidMuleEvent then the MessageSource should wait for the ReplyToHandler to be invoked before sending a response, otherwise the response should be sent immediatly.

Note: If AsyncResponseFlowProcessingPhase is used then non-blocking will be supported, it is still necessary that the MessageSource implements this interface though.

Since:

3.7

Method Summary

Methods inherited from interface org.mule.api.source.MessageSource

setListener