On 12/02/2011 05:58 PM, sreuland wrote:
Hello, I'm trying to create an x-match binding on a headers exchange(qpid 0.10) and it appears as though only the last value for a key is being taken, for example here's the address string:myqueue; {create: always,node: {type: queue, durable:'True',x-declare: {auto-delete:'False', exchange:my_exch, type:headers}, x-bindings:[{queue:myqueue,exchange:'my_exch',arguments:{'x-match':any,'a':'10','a':'999'}}]}} when sending messages to 'my_exch', only those with header a=999 get routed to 'myqueue', it appears as though only the last key value in x-match is taken, is there any way I can specify multiple values for the same key in a single address string via x-match syntax?
Maps can only have one value per key. Even if the address allowed multiple values with the same key, the AMQP protocol wouldn't allow that to be sent across the wire. So unfortunately you cannot have multiple values for the same header in a single binding.
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
