The Routing Slip from the EIP patterns allows you to route a message consecutively through a series of processing steps where the sequence of steps is not known at design time and can vary for each message.
Delimiter used if the Expression returned multiple endpoints.
If an endpoint URI could not be resolved, should it be ignored.
Otherwise, Camel will throw an exception stating the endpoint URI is not valid.
Camel 2.13.1/2.12.4: Allows to configure the cache size for the
The default cache size is
A value of
Messages will be checked for the existence of the
aRoutingSlipHeader header. The value of this header should be a comma-delimited list of endpoint URIs you wish the message to be routed to. The Message will be routed in a pipeline fashion, i.e., one after the other. From Camel 2.5 the Routing Slip will set a property,
Exchange.SLIP_ENDPOINT, on the Exchange which contains the current endpoint as it advanced though the slip. This allows you to know how far we have processed in the slip.
Here we set the header name and the URI delimiter to something different.
Using the Fluent BuildersUsing the Spring XML Extensions
Ignore Invalid Endpoints
Available as of Camel 2.3
And in Spring XML its an attribute on the recipient list tag:
Then let's say the
myHeader contains the following two endpoints
direct:foo,xxx:bar. The first endpoint is valid and works. However the second endpoint is invalid and will just be ignored. Camel logs at
INFO level, so you can see why the endpoint was invalid.
Available as of Camel 2.4
And in Spring XML its an attribute on the recipient list tag.
For further examples of this pattern in use you could look at the routing slip test cases.
Using This Pattern
If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.