Couple of things...
1) I believe Tim is right that you might need to munge the queue name a
bit yourself to deal with portability issues. Of
javax.jms.Session#createQueue, the JavaDoc says, "This facility is provided
for the rare cases where clients need to dynamically manipulate queue
identity
Session.createQueue() is defined as part of the JMS spec, and it's not a
bug when it doesn't do things beyond the requirements of the spec.
Just strip off the prefix yourself before you call it.
Tim
On Oct 2, 2017 5:15 AM, "boekhold" wrote:
Hi,
The following code fails:
String replyDestStr =
Mea culpa,
that code should be:
String replyDestStr = msg.getJMSReplyTo().getQueueName();
// forward the request asynchronously to a 3rd-party system, with
// "replyDestStr" included in the 3rd-party request and response
Queue replyQ = session.createQueue(replyDestStr);
Code tested so far with
Hi,
The following code fails:
String replyDestStr = msg.getJMSReplyTo().toString();
// forward the request asynchronously to a 3rd-party system, with
// "replyDestStr" included in the 3rd-party request and response
Queue replyQ = session.createQueue(replyDestStr);
The problem is that the first l
