My team mate Marek (Hi man!) found a bug/misfunction of RecipientList. We
have just tested it. It seems it uses Pipeline to process the collection of
endpoints. It works in totally different way than the documentation
suggests. It simply sends RS from the first endpoint as a RQ for the next
endpoint. We think that it should work in multicast mode and optionally in
pipeline mode, but multicasting should be default mode (according to docs).
We patched that class changing the processor from Pipeline to
MulticastProcessor and it works for us, but probably it needs either fixing
or improving to be able to choose the required mode. Did we miss something?
What was actually the intent of RecipientList? What can we do about it to
avoid patching that class on our side?
--
View this message in context:
http://www.nabble.com/RecipientList-works-inproperly-tp14731056s22882p14731056.html
Sent from the Camel - Users mailing list archive at Nabble.com.
