Daniel Kulp wrote
> Looking in the code:
>
> public Destination getReplyToDestination(JmsTemplate jmsTemplate,
> Message inMessage) throws JMSException {
> javax.jms.Message message =
> (javax.jms.Message)inMessage.get(JMSConstants.JMS_REQUEST_MESSAGE);
> // If WS-Addressing had set the replyTo header.
> final String replyToName =
> (String)inMessage.get(JMSConstants.JMS_REBASED_REPLY_TO);
> if (replyToName != null) {
> return resolveDestinationName(jmsTemplate, replyToName);
> } else if (message.getJMSReplyTo() != null) {
> return message.getJMSReplyTo();
> } else if (!StringUtils.isEmpty(jmsConfig.getReplyDestination()))
> {
> return resolveDestinationName(jmsTemplate,
> jmsConfig.getReplyDestination());
> } else {
> throw new RuntimeException("No replyTo destination set on
> request message or cxf message");
> }
> }
>
> Thus, if you have an interceptor or similar on the chain, you should be
> able to set the JMSConstants.JMS_REBASED_REPLY_TO property on the IN
> message to something else and it should be picked up.
I'll give that a shot.
Thanks,
Jens
--
View this message in context:
http://cxf.547215.n5.nabble.com/JMS-Transport-Overriding-ReplyDestination-tp5731199p5731255.html
Sent from the cxf-user mailing list archive at Nabble.com.
