Yes, I am dumbing down the scenario and don't mention recovery, threading, etc to focus on the concrete issues how to link up a temp channel. The client specified a requirement of one defined queue per service - I currently have a workaround with one queue and a topic but it's not fully meeting the requirement.
Anyway, your comment gave me something to think about. I was too focused on abstracting away the actual transport protocol but guess have to give up that notion once we deal with a design that requires temp JMS queues... :-) On the initially receiving node it is incorrect to create a temp queue. Instead I should get the actually created temp queue out of the Camel Exchange context (JMSReplyTo) and see how to coerce Camel into using it for sending responses. I have to implement a few other features for a deadline but will give it another try in a couple of days. Cheers und Gruesse! -- View this message in context: http://camel.465427.n5.nabble.com/Issue-with-JMS-Temp-Queues-Tibco-EMS-tp3425694p3782155.html Sent from the Camel - Users mailing list archive at Nabble.com.
