Yes, this fulfill your requirements. Best, Christian
Sent from a mobile device Am 24.05.2012 11:20 schrieb "ppou" <pan...@gmail.com>: > the bean opens a socket to connect to an external service and waits for a > response, however in the current implementation when another Exchange > reaches the bean it also sends the body to the service using the same > connector. This creates conflicts. > > I was wishing to limit the number of exchanges that go to to the bean, and > I > thought it could be done with seda and concurrentConsumers > > -- > View this message in context: > http://camel.465427.n5.nabble.com/seda-concurrent-consumers-tp5713463p5713468.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
