OK, I've testest some use cases... This list is far from being
comprehensive... Looks like only destination names containing "?" that are
accepted by JMS api, will have issues as ActiveMQ parses destination name as
URI string. Consequently, “?” is removed and everything after it is treated
as query params.
destination name
ActiveMQ name
"?test?.jms.spec.que?"
Message ID:dev1467-56629-1362089194289-3:1:1:1:1 sent to queue://
"?test.jms.spec.que"
Message ID:dev1467-56629-1362089194289-9:1:1:1:2 sent to queue://
"test?.jms.spec.que?"
Message ID:dev1467-56629-1362089194289-13:1:1:1:2 sent to queue://test
"#test#.jms.spec.que#"
Message ID:dev1467-56629-1362089194289-17:1:1:1:2 sent to
queue://#test#.jms.spec.que#
"\test.jms.spec.que"
Message ID:dev1467-56629-1362089194289-19:1:1:1:2 sent to
queue://est.jms.spec.que
"\\test.jms.spec.que"
Message ID:dev1467-56629-1362089194289-25:1:1:1:3 sent to
queue://\test.jms.spec.que
"test.jms.spec.que\\"
Message ID:dev1467-56629-1362089194289-33:1:1:1:2 sent to
queue://test.jms.spec.que\
"/test.jms.spec.que"
Message ID:dev1467-56629-1362089194289-37:1:1:1:2 sent to
queue:///test.jms.spec.que
--
View this message in context:
http://activemq.2283324.n4.nabble.com/What-are-limitations-restrictions-on-destination-name-tp4664141p4664275.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
