This content has been marked as final.
Show 3 replies
-
1. Re: Deferred use of JMSReplyTo / Destination.toString()
amit.bhayani Mar 21, 2005 4:28 AM (in response to lekkim)JMS specification does not say anything about naming policy. So the 'queue' prefix is specific to JBoss. Chances of JBoss future relase changing this is very dim, unless JMS Specification changes drastically :)
Amit. -
2. Re: Deferred use of JMSReplyTo / Destination.toString()
adrian.brock Mar 21, 2005 2:32 PM (in response to lekkim)If you cannot maintain the javax.jms.Destination object
you can do session.createQueue(...) from Queue.getQueueName()
provided you are talking to the same jms server. -
3. Re: Deferred use of JMSReplyTo / Destination.toString()
lekkim Mar 21, 2005 4:21 PM (in response to lekkim)"adrian@jboss.org" wrote:
If you cannot maintain the javax.jms.Destination object
you can do session.createQueue(...) from Queue.getQueueName()
provided you are talking to the same jms server.
Yeah I figured as much since the interface doesn't extend java.io.Serializable... The question went more as to whether I could reconstruct the queue name at a later time using "queue/" + msg.getJMSReplyTo().getQueueName() and make sure it worked (per J2EE spec.) or whether the "queue/" prefix had to be a configurable parameter.
Thank you for your response and clarification though.