Soooo is there any "good" reason for not making x-amqp-0-10.routing-key available for JMS clients.
Doing some Googling on this apparently it used to be available (though returned a byte[] not a string) but it got removed as it wasn't a standard JMS property. I can't see any reason why it's not made available - it's really useful for demultiplexing topics if one subscribes to a wildcard, for example to implement client side custom filters. Theres an evil hack that can be used by regexing the "toString" form of getJMSDestination() :-D but it really pains me to have to do that and clearly it could be broken on any new release. If it's good enough for the C++ and python APIs it's good enough for Java. Regards, Frase Gordon Sim wrote: > > On 06/24/2011 05:13 PM, Rajith Attapattu wrote: >> Unfortunately the JMS client doesn't put the routing key in message >> properties when sending messages. >> However I believe the C++ client includes a property called >> ""x-amqp-0-10.routing-key" >> I checked with the C++ version of spout but it didn't seem that >> property was used. > > It's only used for reading the routing key of a received message (you > can control the routing key for messages you sent through the address > name or subject (depending on node type). >> >> Rajith >> > > -- View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/how-do-I-retrieve-the-subject-from-JMS-tp6491033p6611531.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
