Thanks Mark. I reviewed the recipient list pattern in Camel documentation <http://camel.apache.org/recipient-list.html> and do not see how this solves the transform issue. Could you be so kind as to provide a code example?
Upon further reading, I was thinking that a multicast pattern may best suite this use case, like: <camelContext xmlns="http://camel.apache.org/schema/spring";> <route> <from uri="direct:start"/> <multicast> <to uri="direct:a"/> <to uri="direct:b"/> </multicast> </route> <route> <from uri="direct:a"/> <transform> <simple>${in.body} extra data!</simple> </transform> <to uri="mock:a"/> </route> <route> <from uri="direct:b"/> -- original body without "extra data!" <to uri="mock:b"/> </route> </camelContext> Thoughts? -- View this message in context: http://camel.465427.n5.nabble.com/Transform-without-modifying-message-for-downstream-endpoints-tp5747057p5749365.html Sent from the Camel - Users mailing list archive at Nabble.com.
