Camel JMS Consumer doesn’t need to specify the replyTo option from the endpoint, as it just read the JMS property to find out the Jms destination to send the reply message.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On November 19, 2014 at 1:48:13 PM, Gary Kennedy (g...@apnic.net) wrote: > So I want to talk to a system that will send back several reply messages for > a given command > message. > > The general idea is to have a specific route that will process the reply > messages. (maybe > behind an aggregator/resequencer, maybe not) > > Since the plan is to (eventually) use this in a production environment, I > want to use a > temporary queue for the replies rather than a shared queue. > > The basic template at the moment: > > > < !-- magic here -- > > < !-- prep a command message -- > > < !-- now to send the command message -- > > > > > > > > < !-- more magic -- > > > > So the main question is how can I get {{temp-queue}} to expand to the JMS > specific uri of > the Camel uri "jms:temp:queue:client-replies"? > > But if anyone knows how to deal with temporary queues other solutions would > be welcome. > :) > > Cheers, > Gary > >
