Interface | Description |
---|---|
AsyncResponseFlowProcessingPhaseTemplate |
Template methods for
MessageSource specific behavior during
flow execution. |
EndPhaseTemplate |
Phase were the
MessageProcessTemplate is notified that
the message processing has ended |
FlowProcessingPhaseTemplate |
Template methods for
MessageSource specific behavior during
flow execution. |
MessageProcessContext |
Context for processing one message from a
MessageSource . |
MessageProcessingManager |
In charge of processing messages through mule.
|
MessageProcessorExecutionInterceptor |
Intercepts a MessageProcessor execution.
|
MessageProcessPhase<Template extends MessageProcessTemplate> |
Defines a phase that process a message using a
MessageProcessTemplate
The phase will be part of a chain of responsibility were the phase can define
the end of the execution of the set of phases by calling:
- PhaseResultNotifier.phaseConsumedMessage() which indicates that the phase has consume the message
and it should not be longer processed
- PhaseResultNotifier.phaseFailure(Exception) which indicates that there was a failure
during message processing. |
MessageProcessTemplate |
Maker interface for every template that can be used in a
MessageProcessPhase
A MessageProcessTemplate must contain all the required method that redefines behavior
inside a MessageProcessPhase and it's particular from the MessageSource |
PhaseResultNotifier |
Notifier used by
MessageProcessPhase in order to
define the result of the phase execution |
RequestResponseFlowProcessingPhaseTemplate |
Extension of
FlowProcessingPhaseTemplate for those MessageSource
that requires sending a response of the message processed. |
ResponseCompletionCallback |
Callback to be used to notify of the result of an asynchronous response writing task.
|
ThrottlingPhaseTemplate |
Template that a
MessageSource must implement
if it wants to participate in the throttling phase when processing a message |
ValidationPhaseTemplate |
Phase for validation of the incoming message.
|
Class | Description |
---|---|
AsyncResponseFlowProcessingPhase |
This phase routes the message through the flow.
|
EndProcessPhase |
This phase notifies to the
MessageProcessTemplate that the message processing
has ended. |
ErrorHandlingExecutionTemplate |
ExecutionTemplate created by this method should be used on the beginning of the execution of a chain of
MessageProcessor that should manage exceptions.
|
ExceptionToMessagingExceptionExecutionInterceptor |
Replace any exception thrown with a MessagingException
|
ExecutionContext |
Provides information about the current execution of an
ExecutionTemplate |
FlowProcessingPhase |
This phase routes the message through the flow.
|
IsolateCurrentTransactionInterceptor<T> | |
MessageProcessorExecutionTemplate |
Template for executing a MessageProcessor.
|
MuleMessageProcessingManager |
Default implementation for
MessageProcessingManager . |
NotificationFiringProcessingPhase<Template extends MessageProcessTemplate> |
Provides a reusable way for concrete
MessageProcessPhase s to fire notifications. |
PhaseExecutionEngine |
This class process a message through a set of
MessageProcessPhase using
the message content and message processing context provided by MessageProcessTemplate and MessageProcessContext . |
SuspendXaTransactionInterceptor<T> | |
TransactionalErrorHandlingExecutionTemplate |
Creates an execution context that should be used when:
- A flow execution starts because a message was received by a MessageReceiver
- Any other entry point of execution with no parent execution context
Created a ExecutionTemplate that will:
Resolve non xa transactions created before it if the TransactionConfig action requires it
suspend-resume xa transaction created before it if the TransactionConfig action requires it
start a transaction if required by TransactionConfig action
resolve transaction if was started by this TransactionTemplate
route any exception to exception strategy if it was not already routed to it
|
TransactionalExecutionTemplate<T> |
ExecutionTemplate created should be used on a MessageProcessor that are previously wrapper by
TransactionalErrorHandlingExecutionTemplate or ErrorHandlingExecutionTemplate
Should be used when:
An outbound endpoint is called
An outbound router is called
Any other MessageProcessor able to manage transactions is called
Instance of TransactionTemplate created by this method will:
Resolve non xa transactions created before it if the TransactionConfig action requires it
Suspend-Resume xa transaction created before it if the TransactionConfig action requires it
Start a transaction if required by TransactionConfig action
Resolve transaction if was started by this TransactionTemplate
Route any exception to exception strategy if it was not already routed to it
|
ValidationPhase |
This phase validates the incoming message.
|
Exception | Description |
---|---|
ResponseDispatchException |
Exception thrown when there's a failure writing the response using the transport infrastructure.
|
Copyright © 2003–2016 MuleSoft, Inc.. All rights reserved.