qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aidan Skinner (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Assigned: (QPID-1487) AMQDestination.toURL doesn't work and is not backward compatible with .Net client
Date Wed, 26 Nov 2008 17:12:44 GMT

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


Mime
View raw message