You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by dtauzell <da...@tauzell.org> on 2013/04/03 15:44:22 UTC
Re: Splitter, Aggregation and Timeouts
Thanks,
Is there a way to have the multicast send some sort of parameter to the
direct endpoints so they can all act slightly differently based on that?
Based on the incoming message I will look up N "member ids". Each of those
ids will result in a message being sent to an external web service. Those
message will all be different based on configuration data assoicated with
the "member ids".
-Dave
--
View this message in context: http://camel.465427.n5.nabble.com/Splitter-Aggregation-and-Timeouts-tp5730087p5730282.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Splitter, Aggregation and Timeouts
Posted by Raul Kripalani <ra...@evosent.com>.
Take a look at the "Using a Pojo to do the splitting" section in the Split
EIP docs.
I can't give you a deep link now, sorry.
Regards,
Raúl.
On 5 Apr 2013 01:14, "Raul Kripalani" <ra...@evosent.com> wrote:
> Then you're really after a split pattern rather than a multicast.
>
> Create a bean that does the lookup and returns a List of ids.
>
> Then plug it into the split EIP with:
>
> .split(method(MyBean.class)).
>
> The splitter will process each List element individually.
>
> Regards,
> Raúl.
> Thanks,
>
> Is there a way to have the multicast send some sort of parameter to the
> direct endpoints so they can all act slightly differently based on that?
>
> Based on the incoming message I will look up N "member ids". Each of those
> ids will result in a message being sent to an external web service. Those
> message will all be different based on configuration data assoicated with
> the "member ids".
>
> -Dave
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Splitter-Aggregation-and-Timeouts-tp5730087p5730282.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Splitter, Aggregation and Timeouts
Posted by Raul Kripalani <ra...@evosent.com>.
Then you're really after a split pattern rather than a multicast.
Create a bean that does the lookup and returns a List of ids.
Then plug it into the split EIP with:
.split(method(MyBean.class)).
The splitter will process each List element individually.
Regards,
Raúl.
Thanks,
Is there a way to have the multicast send some sort of parameter to the
direct endpoints so they can all act slightly differently based on that?
Based on the incoming message I will look up N "member ids". Each of those
ids will result in a message being sent to an external web service. Those
message will all be different based on configuration data assoicated with
the "member ids".
-Dave
--
View this message in context:
http://camel.465427.n5.nabble.com/Splitter-Aggregation-and-Timeouts-tp5730087p5730282.html
Sent from the Camel - Users mailing list archive at Nabble.com.