Hi there, I just used the concurrentConsumers parameter of the seda component and fell into the trap of not including parameters in the producer URI. Having to have the producer and consumer specify the same parameters seems troublesome and non-intuitive. Additionally the producer URI shouldn't have to concern itself with how the exchange will be consumed and doesn't elsewhere in Camel.
Do you think that this should be recognised as an issue to be fixed? Kind regards, Christopher -- View this message in context: http://www.nabble.com/seda-uris-for-producers-and-consumers-tp24735545p24735545.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
