The toString() representation of the JMSDestination of a received message is different from the toString() representation on the sender side

The value of toString() on the JMS Destination of a message being sent is different from to the toString() value of JMS Destination of the same message on the receiver side.

Ex for clients using the BURL syntax.

Sender side
The JMSDestination on the sent message is
"direct://amq.direct//testQueue?routingkey='key1'"

Receiver side
The JMSDestination on the recvd message is
"direct://amq.direct/key1/key1?routingkey='key1'"

Ex for client using the ADDR syntax.

Sender side
JMS Destination: 'amq.direct'/'test'; None

Receiver side
JMS Destination: direct://amq.direct/test/test?routingkey='test'

How reproducible:
Always

Steps to Reproduce:
1. Use spout to send a message and observe the JMS Destination printed on the screen.
2. Use drain to receive that message and observe the same.
3. Note that they are represented differently.

Actual results:
The toString representations are different.
(However they contain the correct exchange and routing key information).

Expected results:
The toString representations should be the same.