org.mule.execution
Interface MessageProcessContext

All Known Implementing Classes:

AbstractTransportMessageProcessTemplate, HttpMessageProcessTemplate, HttpsMessageProcessTemplate

public interface MessageProcessContext

Context for processing one message from a MessageSource. Mule MessageSource implementations should create one instance of MessageProcessContext per message that generates. MessageProcessContext is responsible for - Define if the incoming message can be processed in a separate thread - Provide access to the MessageSource of the message - Provide access to the FlowConstruct were the message is going to be executed - Provide access, if available, to the WorkManager to use for processing the message - Provide the MessageSource transaction configuration

Method Summary

FlowConstruct	getFlowConstruct()
WorkManager	getFlowExecutionWorkManager()
MessageSource	getMessageSource()
TransactionConfig	getTransactionConfig()
boolean	supportsAsynchronousProcessing()

Method Detail

supportsAsynchronousProcessing

boolean supportsAsynchronousProcessing()

Returns:

true if the message can be processed in a different thread than the one it was acquired, false otherwise

getMessageSource

MessageSource getMessageSource()

Returns:

the MessageSource that retrieve the message. Can not be null

getFlowConstruct

FlowConstruct getFlowConstruct()

Returns:

the FlowConstruct were the incoming message is going to be executed. Can not be null

getFlowExecutionWorkManager

WorkManager getFlowExecutionWorkManager()

Returns:

the WorkManager were the incoming message must be processed. If null it will be executed in the same thread were the message was received

getTransactionConfig

TransactionConfig getTransactionConfig()

Returns:

the TransactionConfig associated to the MessageSource that received the message. If null then no transaction config will be used.