On Thu, May 14, 2009 at 8:51 AM, Frank Schwarz <[email protected]> wrote: > > Hi Claus, > > > JMS broker is JBoss Messaging in JBoss AS 5.0.0. > > > I did some debugging though. It seems to be that in > JMSProducer#process(Exchange) > > > > if (!endpoint.isPreserveMessageQos() && !endpoint.isExplicitQosEnabled() && > exchange.getIn().getHeaders().containsKey("JMSReplyTo")) > > > is not quite correct in my environment as > > > > exchange.getIn().getHeaders().containsKey("JMSReplyTo") == true, > > > but > > > > exchange.getIn().getHeaders().get("JMSReplyTo") == null > Hi Frank
Ah thanks so the JMSReplyTo key is there but its null. I got it. Do you mind creating a JIRA ticket for it, then I will fix it ASAP. Just refer to this using nabble. > > > HTH, > > Frank > > > > Claus Ibsen-2 wrote: >> >> Hi >> >> Can you show the route DSL. Looks like the Exchange is InOnly but the >> JMS Broker still sets a JMSReplyTo header. >> >> What JMS broker are you using, and version? >> Which Container are you using, and version? >> > > -- > View this message in context: > http://www.nabble.com/Disabling-JMSReplyTo-as-this-Exchange-is-not-OUT-capable-tp23524909p23535341.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
