Update: It works.
>From my point of view, it would be nice to extend camel to support provider
specific JMS destination properties.
I'm not yet sure how to include it. Maybe it could be done just by have the
possiblity to add a "DestinationPropertyProvider" or something like this
just at the place where I added my properties.
An aspect to consider is, that the JMSReplyTo (destination) proviced by the
JMS-Message could contain already properties. In my case the targetClient=1
is already specified and this property works correctly.
What I had to set was for example:
mqDestination.setMQMDMessageContext(CommonConstants.WMQ_MDCTX_SET_IDENTITY_CONTEXT);
I have to check with my boss if I'm allowed to spend time to contribute the
solution for that.
--
View this message in context:
http://camel.465427.n5.nabble.com/DestinationResolver-for-Reply-Messages-tp5727490p5727771.html
Sent from the Camel - Users mailing list archive at Nabble.com.
