You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <ji...@apache.org> on 2011/05/21 03:19:47 UTC
[jira] [Created] (QPID-3271) The toString() representation of the
JMSDestination of a received message is different from the toString()
representation on the sender side
The toString() representation of the JMSDestination of a received message is different from the toString() representation on the sender side
--------------------------------------------------------------------------------------------------------------------------------------------
Key: QPID-3271
URL: https://issues.apache.org/jira/browse/QPID-3271
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.10, 0.8
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: 0.11
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Closed] (QPID-3271) The toString() representation of the
JMSDestination of a received message is different from the toString()
representation on the sender side
Posted by "Rajith Attapattu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu closed QPID-3271.
----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: Future)
Future client work involves parsing both BURL and Address formats into an internal data structure. When we get to this a proper toString() method for this internal data structure would easily solve this issue.
It's not worth the effort to fix this in the current client as we have already begun work with the new clients.
> The toString() representation of the JMSDestination of a received message is different from the toString() representation on the sender side
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3271
> URL: https://issues.apache.org/jira/browse/QPID-3271
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.8, 0.10
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Labels: addressing
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-3271) The toString() representation of the
JMSDestination of a received message is different from the toString()
representation on the sender side
Posted by "Robbie Gemmell (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-3271:
---------------------------------
Fix Version/s: (was: 0.11)
Future
> The toString() representation of the JMSDestination of a received message is different from the toString() representation on the sender side
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3271
> URL: https://issues.apache.org/jira/browse/QPID-3271
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.8, 0.10
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Fix For: Future
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org