This bug fix seems to be a partial fix, which was part of 5.13.3.
stompconnection.send("queue://test.aanto1.queue,topic://test.aanto2.topic",
"messsage1", "tx1", null);
=> PASS: creates QUEUE "test.aanto1.queue"
=> FAIL: creates QUEUE "topic://test.aanto2.topic", instead of creating a
TOPIC "test.aanto2.topic"
stompconnection.send("test.aanto1.queue,queue://test.aanto2.queue",
"messsage1", "tx1", null);
=> PASS: creates QUEUE "test.aanto1.queue"
=> FAIL: creates QUEUE "queue://test.aanto2.queue", instead of creating a
QUEUE "test.aanto2.queue"
stompconnection.send("topic://test.aanto1.topic,topic://test.aanto2.topic",
"messsage1", "tx1", null);
=> PASS: creates TOPIC "test.aanto1.topic"
=> FAIL: creates QUEUE "topic://test.aanto2.topic", instead of creating a
TOPIC "test.aanto2.topic"
Thank you
Aanto.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-0-Bug-in-Composite-Destination-using-Stomp-tp4710740p4712878.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
