The seda component allows to specify a number of concurrent consumers, so can you process messages in parallel if you want.
When you send a message to a seda endpoint it depends if its InOnly or InOut. The latter will have the sender wait for the message to complete (but you can configure this). See the seda page for more details http://camel.apache.org/seda On Thu, May 2, 2013 at 12:03 PM, anand_tech <anand29...@gmail.com> wrote: > Thanks, can you also have a look at the last part of my question i.e. route > having both direct and seda component. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Back-to-Basics-Apache-Camel-Routes-and-Direct-Component-tp5731899p5731903.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
