Sounds like JMS message groups can help with this. If you use ActiveMQ check out its docs about this.
On Wed, Aug 7, 2013 at 9:24 PM, bocamel <johnz...@gmail.com> wrote: > I need to process orders from multiple companies and then send them out. The > logic for processing is almost identical but I need to send all messages > from a company out in the exact sequence as they are received. Therefore, > I would like to have concurrency but need to apply concurrency only when the > messages are for different companies. Another way to say this is that, I > want all messages from one company to be processed singled threaded. One > way that I can do this is to route the messages into different SEDA queues > based on the company names. Then process messages from each SEDA queue > single threaded. But I do not want to duplicate my route definition for > each company in my Spring xml file (to consume from each separate SEDA > queue). Is there an elegant way to do this (in Camel with Spring)? > > Thanks in advance! > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Limit-concurrency-to-messages-with-different-headers-tp5736945.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
