You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by PhilBurress <nm...@amig.com> on 2012/07/16 18:07:22 UTC
Multicast question
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.
Re: Multicast question
Posted by PhilBurress <nm...@amig.com>.
By the way, we are stuck on Camel 2.6. I see that there is a callback to do
this in 2.8.
--
View this message in context: http://camel.465427.n5.nabble.com/Multicast-question-tp5716086p5716087.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Multicast question
Posted by Claus Ibsen <cl...@gmail.com>.
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 <nm...@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: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: Multicast question
Posted by Christian Müller <ch...@gmail.com>.
Is your issue related to this one?
https://issues.apache.org/jira/browse/CAMEL-5338
If it is, and you have to stick with a version < 2.8.0, you have to roll
your own solution. You could e.g. make a deep copy of your body and work
with this instance. Than the other routes are not affected for this change.
Best,
Christian
On Mon, Jul 16, 2012 at 6:07 PM, PhilBurress <nm...@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.
>