I've been reading through the source for the JmsProducer class and don't see
how this can ever work for InOnly. It seems that the code is looking at the
inMessage in the Exchange for a ReplyTo header, and not checking the
endpoint definition to see if it's forcing the ReplyTo in the endpoint
definition.
// if the binding did not create the reply to then we have
to try to create it here
String replyTo = exchange.getIn().getHeader("JMSReplyTo",
String.class);
Contrasting this with the InOut model where it uses endpoint.getReplyTo() to
find the replyTo queue.
Am I missing something?
Ian
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-ReplyTo-not-sent-for-InOnly-Pattern-tp3250344p3250848.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.