Thanks Claus, I will certainly take a look at doing that.
In the interim, I used your suggestion of a destination resolver. I am now
overriding the default behaviour when its needed by injecting a destination
resolver under certain conditions which is working fine for now. The better
solution o
Hi
Thanks for the analysis. You can log a JIRA in the issue tracker
(there is a link from this page)
http://camel.apache.org/support.html
You are welcome to dive into the source code in camel-jms to see if
you can find where that normalization is and fix so it only prefix
with double slashes.
htt
Hi Claus, I am starting to think that perhaps this is a bug within the Camel
JMS framework (I could be wrong).
What appears to be happening when it comes to the replyTo queue name is the
Queue Name value is “normalised” incorrectly. As I understand things, if the
replyTo queue is specified with
Hi
I think there is some destination resolver spi you can configure on
the component/endpoint where you can add your java code to build the
queue name using the IBM MQ client api.
On Mon, Feb 26, 2018 at 12:42 PM, Paul Broughton Spida Solutions
wrote:
> Hi, I have a toD element in my route wh
Hi, I have a toD element in my route which sends to a jms Queue which is
provided by IBM MQ. I have the CamelJMSDestinationName set to the queue and a
uri which looks similar to the folowing
wmq:queue:placeholder?preserveMessageQos=true&replyTo=myQM/myTestQ&exchangePattern=inOut&replyToType=shar
