@Steve I'm fairly certain the ProducerTemplate is simply an object and doesn't have its own separate thread. That would create a lot of different problems given the nature of the methods on the ProducerTemplate and the @EndpointInject.
Even when you make async calls using it the PT uses an ExecutorService which has a thread pool. But how else are you going to do an async call with or with Callback/Future? Having the ExectorService at least means you aren't spinning up a lot of new threads and then throwing them away. On Wed, Oct 26, 2016 at 6:44 AM, raghavender.anth...@gmail.com < raghavender.anth...@gmail.com> wrote: > Thanks a ton everyone, I was able to achieve it by using split and by > writing > a custom bean/method. > > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Dynamic-routing-based-on-collection-values-tp5789157p5789282.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
