Hi You can store whatever information you want as exchange properties, and refer to them at any time. So you can for example copy the input message and store it as an exchange. And then get it back from your sub routes.
On Mon, Jul 16, 2012 at 6:07 PM, PhilBurress <nmclough...@amig.com> wrote: > Why isn't the original "in" body of an exchange passed to a route under a > multicast? e.g.: > > > > The original "in" body in those subroutes ends up being the "in" body at the > point the multicast is triggered. > > Is there anyway around this? We need to keep the original exchange "in" body > as it was from the incoming queue in the subroutes. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Multicast-question-tp5716086.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
