[ 
https://issues.apache.org/jira/browse/QPID-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-3265:
---------------------------------

    Fix Version/s:     (was: 0.15)

Removing the released-version 0.15 fix-for, doenst seem like anything has been 
done on this except a small commit which says in its log that it doesnt fix the 
issue....
                
> Can't subscribe to headers exchange using address (rather than BURL)
> --------------------------------------------------------------------
>
>                 Key: QPID-3265
>                 URL: https://issues.apache.org/jira/browse/QPID-3265
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.10
>         Environment: java 0.10 client
>            Reporter: Gordon Sim
>            Assignee: Rajith Attapattu
>              Labels: addressing
>
> Creating a receiver for the following address works from python and c++, but 
> not from JMS (using drain example in each case):
>   my-headers-exchange; 
> {link:{x-bindings:[{arguments:{'x-match':all,a:b,c:d}}]}}
> The problem with JMS seems to be that though it correctly interprets the 
> arguments and issues a bind with them in it, it issues another bind to the 
> exchange with no arguments that fails with an error.
> Also, the following also doesn't work:
>   my-subscription-queue; {create:always, node:{x-declare:{auto-delete:True}}, 
> link:{x-bindings:[{queue:my-subscription-queue, exchange:my-headers-exchange, 
> arguments:{'x-match':all,a:b,c:d}}]}}
> Here the x-bindings in the link don't seem to get interpreted. However if 
> instead they are moved to the node, that works.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to