Hello All,

We are in process of implementing hundreds of routes that will use Camel.
Many of the routes will use remote instance of AMQ, local AMQ or WMQ to
process the messages. Each of the routes will have the same (connection
pooling) code/configuration repeated to connect to any one of these
resources. Is there any solution that can reduce this boiler plate
code/configuration. 

Thanks,
Pravin



--
View this message in context: 
http://camel.465427.n5.nabble.com/JMS-Component-configurations-tp5787499.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to