You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Steven Shaw (JIRA)" <qp...@incubator.apache.org> on 2006/11/14 19:41:37 UTC
[jira] Created: (QPID-96) Change ReplyTo encoding
Change ReplyTo encoding
-----------------------
Key: QPID-96
URL: http://issues.apache.org/jira/browse/QPID-96
Project: Qpid
Issue Type: Improvement
Reporter: Steven Shaw
Priority: Minor
The encoding for the ReplyTo header is currently only allows for Queue/direct and Topic exchanges using a 'Q' and 'T' prefix followed by the queue-name. This needs to be changed to "ExchangeName:QueueName" in order to allow for client-side declared exchanges (which is particularly important for the headers exchange).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (QPID-96) Change ReplyTo encoding
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack reassigned QPID-96:
------------------------------------
Assignee: Robert Greig
Should be done as part of a wider fix to Destination to separate out the concept of a destination from its declaration properties
> Change ReplyTo encoding
> -----------------------
>
> Key: QPID-96
> URL: https://issues.apache.org/jira/browse/QPID-96
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Steven Shaw
> Assigned To: Robert Greig
> Priority: Minor
>
> The encoding for the ReplyTo header is currently only allows for Queue/direct and Topic exchanges using a 'Q' and 'T' prefix followed by the queue-name. This needs to be changed to "ExchangeName:QueueName" in order to allow for client-side declared exchanges (which is particularly important for the headers exchange).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (QPID-96) Change ReplyTo encoding
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey closed QPID-96.
---------------------------
Resolution: Fixed
This encoding has been changed prior to M2
> Change ReplyTo encoding
> -----------------------
>
> Key: QPID-96
> URL: https://issues.apache.org/jira/browse/QPID-96
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Steven Shaw
> Assignee: Robert Greig
> Priority: Minor
>
> The encoding for the ReplyTo header is currently only allows for Queue/direct and Topic exchanges using a 'Q' and 'T' prefix followed by the queue-name. This needs to be changed to "ExchangeName:QueueName" in order to allow for client-side declared exchanges (which is particularly important for the headers exchange).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-96) Change ReplyTo encoding
Posted by "Steven Shaw (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-96?page=all ]
Steven Shaw updated QPID-96:
----------------------------
Component/s: Java Client
> Change ReplyTo encoding
> -----------------------
>
> Key: QPID-96
> URL: http://issues.apache.org/jira/browse/QPID-96
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Steven Shaw
> Priority: Minor
>
> The encoding for the ReplyTo header is currently only allows for Queue/direct and Topic exchanges using a 'Q' and 'T' prefix followed by the queue-name. This needs to be changed to "ExchangeName:QueueName" in order to allow for client-side declared exchanges (which is particularly important for the headers exchange).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira