Hi
I've noticed some slightly weird behaviour with respect to bindings.
I've got a Java test consumer client with an address string in JNDI as
follows
destination.subscribedAddress1 = test; {create: always, node:
{x-bindings: [{exchange: 'amq.direct', queue: 'test', key: 'test'}]}}
So
On 12/09/2011 02:15 PM, Alan Conway wrote:
On 12/09/2011 08:57 AM, Fraser Adams wrote:
Hi
I've noticed some slightly weird behaviour with respect to bindings.
I've got a Java test consumer client with an address string in JNDI as
follows
destination.subscribedAddress1 = test; {create: always,
Ahhh thanks Alan,
To be honest I've never really figured out what the difference is
between node and link blocks in address strings.
Is there a good explanation anywhere about the distinction between nodes
and links. Most of the info on address strings is in the Programming in
Apache Qpid
This is an area that has been underspecified. The c++ client will
create the binding if it does not exist even if the node already exists.
The python client only considers the binding if the node doesn't
exist. It sounds like the JMS client does the same.
Personally I think the former
