camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kraythe ." <kray...@gmail.com>
Subject Re: RecipientList or DynamicRouter or RoutingSlip
Date Sat, 21 Dec 2013 15:33:17 GMT
Typically you would use a recipient list if there are potentially more than
one receiver or if the receiver is not known at compile time. So if you
have a record where the receiver is calculated off some data from another
system you would use a recipient list. If you have known routing situation
at compile time you would use a dynamic router because dynamic routers have
much clearer semantics when you look at the code.

On Saturday, December 21, 2013, Henrique Viecili wrote:

> The requirement seems a bit odd as the receiver header could be derived at
> the consumer, anyway you may be able to access the
> Exchange.RECIPIENT_LIST_ENDPOINT property or perhaps try setting
> onPrepareRef with a custom processor to figure out the header.
>
> Henrique Viecili
>
>
> On 20 December 2013 19:13, ABouchama <titexe@yahoo.fr <javascript:;>>
> wrote:
>
> > Thanks for your reply,
> >
> > The Dynamic RecipientList allow only to send the same messages to a
> Dynamic
> > list of endpoints.
> >
> > My need, is to send the same message and overriding his header=Receiver
> > following endpoints
> > Receiver=A for endpoint =A
> > Receiver=B for endpoint =B ...etc
> >
> > Thanks for help
> >
> >
> >
> > --
> > View this message in context:
> >
> http://camel.465427.n5.nabble.com/RecipientList-or-DynamicRouter-or-RoutingSlip-tp5745069p5745092.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
>


-- 
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA*
*Author of: Hardcore Java (2003) and Maintainable Java (2012)*
*LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39
<http://www.linkedin.com/pub/robert-simmons/40/852/a39>*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message