[
https://issues.apache.org/jira/browse/QPID-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-741.
-----------------------------------
Resolution: Won't Fix
The destination is used in DurableTopicSubscriptions.
It is best to address any issues when we look at refactoring the BindingURL
alltogether.
Currently there are several aspects that cannot be sucessfully handled via the
current binding URL.
> The BindingURL format is incorrect
> ----------------------------------
>
> Key: QPID-741
> URL: https://issues.apache.org/jira/browse/QPID-741
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M3
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: M4
>
>
> The binding URL is defined as follows.
> <exch_class>://<exch_name>/[<destination>]/[<queue>]?<option>='<value>'[,<option>='<value>']*
> RoutingKey is given as a valid option (See BindingURL class) and the
> following documentation http://cwiki.apache.org/qpid/bindingurlformat.html.
> Then in AMQDestination we see that the constructors has a field called
> "destinationName" (in addition to exchangeName).
> As per the AMQP spec, destination refers to the exchange you are publishing.
> Therefore the binding url format is incorrect, as destination has no meaning
> in the URL.
> It cannot be the routing_key as it is given as a valid option. So I propose
> we get rid of it.
> However the documentation here is correct, but sadly not reflected in the
> code properly.
> http://cwiki.apache.org/qpid/bindingurlformat.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
