You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org> on 2008/11/25 17:35:47 UTC
[jira] Created: (QPID-1487) java client URLs are not backward
compatible with .Net client
java client URLs are not backward compatible with .Net client
-------------------------------------------------------------
Key: QPID-1487
URL: https://issues.apache.org/jira/browse/QPID-1487
Project: Qpid
Issue Type: Bug
Components: Dot Net Client, Java Client
Reporter: Aidan Skinner
Assignee: Aidan Skinner
Fix For: M4
The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (QPID-1487) AMQDestination.toURL doesn't work and
is not backward compatible with .Net client
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner reassigned QPID-1487:
-----------------------------------
Assignee: Rajith Attapattu (was: Aidan Skinner)
I've fixed the immediate problem and added a test, and removed some dead files. This area is a huge mess though and should be sorted out for M4+1.
> AMQDestination.toURL doesn't work and is not backward compatible with .Net client
> ---------------------------------------------------------------------------------
>
> Key: QPID-1487
> URL: https://issues.apache.org/jira/browse/QPID-1487
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Client
> Reporter: Aidan Skinner
> Assignee: Rajith Attapattu
> Fix For: M4
>
>
> The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
> Also problematically, it totally ignores the bindingKey parameter. It's not possible to construct a destination with a null routingkey except by passing in an already existing binding url.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1487) AMQDestination.toURL doesn't work and
is not backward compatible with .Net client
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-1487:
-----------------------------------
Assignee: Aidan Skinner (was: Rajith Attapattu)
> AMQDestination.toURL doesn't work and is not backward compatible with .Net client
> ---------------------------------------------------------------------------------
>
> Key: QPID-1487
> URL: https://issues.apache.org/jira/browse/QPID-1487
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Client
> Reporter: Aidan Skinner
> Assignee: Aidan Skinner
> Fix For: M4
>
>
> The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
> Also problematically, it totally ignores the bindingKey parameter. It's not possible to construct a destination with a null routingkey except by passing in an already existing binding url.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1487) AMQDestination.toURL doesn't work and
is not backward compatible with .Net client
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651589#action_12651589 ]
Rajith Attapattu commented on QPID-1487:
----------------------------------------
Aidan,
I have looked at the modification and the test cases added and it looks good to me.
Also I am glad that you have cleaned up the dead classes. There are few more classes like that, and I am planning to get rid of them post M4.
> AMQDestination.toURL doesn't work and is not backward compatible with .Net client
> ---------------------------------------------------------------------------------
>
> Key: QPID-1487
> URL: https://issues.apache.org/jira/browse/QPID-1487
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Client
> Reporter: Aidan Skinner
> Assignee: Rajith Attapattu
> Fix For: M4
>
>
> The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
> Also problematically, it totally ignores the bindingKey parameter. It's not possible to construct a destination with a null routingkey except by passing in an already existing binding url.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-1487) AMQDestination.toURL doesn't work and
is not backward compatible with .Net client
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-1487.
---------------------------------
Resolution: Fixed
> AMQDestination.toURL doesn't work and is not backward compatible with .Net client
> ---------------------------------------------------------------------------------
>
> Key: QPID-1487
> URL: https://issues.apache.org/jira/browse/QPID-1487
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Client
> Reporter: Aidan Skinner
> Assignee: Aidan Skinner
> Fix For: M4
>
>
> The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
> Also problematically, it totally ignores the bindingKey parameter. It's not possible to construct a destination with a null routingkey except by passing in an already existing binding url.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1487) AMQDestination.toURL doesn't work and
is not backward compatible with .Net client
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner updated QPID-1487:
--------------------------------
Description:
The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
Also problematically, it totally ignores the bindingKey parameter. It's not possible to construct a destination with a null routingkey except by passing in an already existing binding url.
was:The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
Summary: AMQDestination.toURL doesn't work and is not backward compatible with .Net client (was: java client URLs are not backward compatible with .Net client)
> AMQDestination.toURL doesn't work and is not backward compatible with .Net client
> ---------------------------------------------------------------------------------
>
> Key: QPID-1487
> URL: https://issues.apache.org/jira/browse/QPID-1487
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Client
> Reporter: Aidan Skinner
> Assignee: Aidan Skinner
> Fix For: M4
>
>
> The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
> Also problematically, it totally ignores the bindingKey parameter. It's not possible to construct a destination with a null routingkey except by passing in an already existing binding url.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1487) AMQDestination.toURL doesn't work and
is not backward compatible with .Net client
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner updated QPID-1487:
--------------------------------
Status: Ready To Review (was: In Progress)
> AMQDestination.toURL doesn't work and is not backward compatible with .Net client
> ---------------------------------------------------------------------------------
>
> Key: QPID-1487
> URL: https://issues.apache.org/jira/browse/QPID-1487
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client, Java Client
> Reporter: Aidan Skinner
> Assignee: Aidan Skinner
> Fix For: M4
>
>
> The .Net client doesn't understand binding urls without the destination. The java client no longer produces urls with destination, it just encodes everything as a routing key parameter. This is unfortunate.
> Also problematically, it totally ignores the bindingKey parameter. It's not possible to construct a destination with a null routingkey except by passing in an already existing binding url.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.