Hi I haven't had time to look into this.
There may be an issue on the producer side to send a message as InOnly to a JMS destination and preserving the JMSReplyTo header. Fell free to create a little sample project with a couple of routes which highlights your intention. Then we can use that for unit tests and implementing this in camel-jms if an option is missing. On Thu, Nov 4, 2010 at 9:35 PM, igoldsmith <[email protected]> wrote: > > 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. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
