You could use one queue and jms selectors. See:
http://camel.465427.n5.nabble.com/JMS-filtering-based-on-selector-td3229317.html
Christian
Am 30.09.2011 18:45, schrieb sanjai:
Each queue contains data for a separate customer. Customers can pull data
from their queue indirectly via a web service call they make to us which
pulls from the company queues and return the resulting messages. However,
there are some customers who want us to "push" data to them by calling their
web service.
It is this second scenario I need to implement. Since all this data is
handled the same way, I just wanted one route which reads from these queues,
processes the data, and sends the data to the customer by calling their web
service endpoint. I can try Claus's suggestion. Another option is to
change the process that writes to the queues to only write to one common
queue, but I was hoping to avoid that.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-consume-from-multiple-JMS-queues-tp4857383p4857780.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
