On Sat, Dec 5, 2009 at 9:20 AM, mcrive <mcr...@optasportsdata.com> wrote: > > Nice one. > Can you suggest a way to achieve what I need to do with Camel 2.1? > >
1) Yeah you could send them message yourself from a processor / bean and use the producerTemplate which has an async variation See more at http://camel.apache.org/async 2) Or create your own recipient list processor which is inspired by the code changes committed. You just extend the existing recipient list, override the method that leverages the MulticastProcessor where you indicate true for parallel. And then use it just as a regular processor from(x).to(new MyPrallelRecipientList()); > > Claus Ibsen-2 wrote: >> >> No but we got a ticket for it >> https://issues.apache.org/activemq/browse/CAMEL-2223 >> >> And its possible to implement as the underlying logic supports it - so >> its merely just to expose the settings. >> We should get that into Camel 2.2 then :) >> > > -- > View this message in context: > http://old.nabble.com/recipientList-multithreading-tp26635868p26653717.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
