org.mule.api.routing
Interface OutboundRouterCatchAllStrategy
- All Superinterfaces:
- MessageProcessor
- All Known Implementing Classes:
- AbstractCatchAllStrategy, ForwardingCatchAllStrategy, LoggingCatchAllStrategy, ServiceCatchAllStrategy
public interface OutboundRouterCatchAllStrategy
- extends MessageProcessor
RouterCatchAllStrategy
is a strategy interface that allows developers to hook in custom code when
an event is being routed on the inbound or outbound but does not match any of the criteria defined for the routing.
Think of catch all strategies as a safety net for your events to ensure that all events will get processed. If you
do not use conditional routing logic, you will not need a catch all strategy.
Method Summary |
MuleEvent |
process(MuleEvent event)
This method will be invoked when an event is received or being sent where the criteria of the router(s) do not
match the current event. |
process
MuleEvent process(MuleEvent event)
throws RoutingException
- This method will be invoked when an event is received or being sent where the criteria of the router(s) do not
match the current event.
- Specified by:
process
in interface MessageProcessor
- Parameters:
event
- the current event being processed
- Returns:
- A result message from this processing. Depending on the messaging style being used this might become the
response message to a client or remote service call.
- Throws:
RoutingException
- if there is a failure while processing this message.
Copyright © 2003-2014 MuleSoft, Inc.. All Rights Reserved.