Use the recipient list EIP and transform only on one branch.
> On Feb 10, 2014, at 5:27 PM, MichaelAtSAG <mebevilac...@gmail.com> wrote: > > Is it possible to nest a transform so that it does not alter the original > message payload? > > This alters original payload: > > <camelContext xmlns="http://camel.apache.org/schema/spring";> > <route> > <from uri="direct:start"/> > <transform> > <simple>${in.body} extra data!</simple> > </transform> > <to uri="mock:end"/> > </route> > </camelContext> > > In psuedo-code, I want to isolate the message transform from downstream > endpoints: > > <camelContext xmlns="http://camel.apache.org/schema/spring";> > <route> > <from uri="direct:start"/> > <isolate> > <transform> > <simple>${in.body} extra data!</simple> > <to uri="mock:end"/> > </transform> > </isolate> > -- original body without "extra data!" > <to uri="mock:end"/> > </route> > </camelContext> > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Transform-without-modifying-message-for-downstream-endpoints-tp5747057.html > Sent from the Camel - Users mailing list archive at Nabble.com.
