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/26 12:24:46 UTC

[jira] Updated: (QPID-1487) AMQDestination.toURL doesn't work and is not backward compatible with .Net client

     [ 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.