[
https://issues.apache.org/activemq/browse/CAMEL-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41849#action_41849
]
Jonathan Anstey commented on CAMEL-365:
---------------------------------------
The two patterns are similar in that they chain together several endpoints. The
routing slip pattern is a bit more dynamic though since the endpoint list is
defined at runtime in a message header.
For example, take a pipeline ala
{code}
from("direct:a").pipeline("direct:x", "direct:y", "direct:z", "mock:result");
{code}
In order to route is this way using the routing slip pattern, you would create
a route like
{code}
from("direct:a").routingSlip();
{code}
and send a message to direct:a with a routing slip header that contains the
list of URIs (direct:x, direct:y, direct:z, and mock:result). You can't do this
in the current build though, I'm still working on it ;)
> implement the Routing Slip pattern
> ----------------------------------
>
> Key: CAMEL-365
> URL: https://issues.apache.org/activemq/browse/CAMEL-365
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: James Strachan
> Assignee: Jonathan Anstey
>
> http://www.enterpriseintegrationpatterns.com/RoutingTable.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
