Hi If you need both components to receive the *same* copy of the message, then you can use the multicast EIP http://camel.apache.org/multicast.html
On Wed, Nov 16, 2011 at 5:12 PM, Diego Manilla <[email protected]> wrote: > Hi. We want to build a couple of generic Components that expect a simple > String in the message body. > > We'll be reading from a JMS queue. This is how the route looks like: > > activemeq:whatever -> component1:whatever -> component2:whatever > > The thing is that the message body coming from the JMS queue is in XML > format, so we would like to extract the relevant parts using an XPath > expression. > > So we tried to add a transformation step between the JMS queue read and the > first component. It works, but because the message is transformed, when it > reaches component2 it is just a String instead of the XML, what makes sense > because the message has been, well, transformed. > > Is there any way to apply a "scoped" transformation or just to perform an > adaptation for the message before it reaches the component, but leaving the > original message intact? > > Thanks in advance. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Non-persistent-transformation-how-to-adapt-the-message-tp4998218p4998218.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
