Hi Siamak,
I've had a look in the Headers Exchange code and traced through the match() code. I've drilled down to the FieldValue impl, which is ultimately where it decides on a match (the operator==() method), someone else please jump in here but what I'm seeing is no support for wild-carding on header values. I know from the docs, that the XML Exchange supports # and * (multiple/single words) as wildcards but from my *very* brief look at the code I'm not seeing that support in the Headers Exchange. This could be a bug but I'll wait for more experienced qpid heads than mine to give their 2c. As I am also fairly new to the code base, its very possible that the wildcarding support may be built into a class that I'm not familiar with. From what I've seen in the FieldValue class, its doing a direct compare to get a match.
all the best, and sorry I couldn't give you a better answer :)
Sam

Sam Joyce wrote:
Hi Siamak,
can you mail me a snippit of your code and I can try to figure out what's going wrong.
thanks,
Sam.

Siamak Kolahi wrote:
Hi guys,

I am new to qpid and I have got a question for you guys. I am trying to
setup a Headers Exchange through the qpid which routs based on headers. As I
am seeing in AMQP spec, the headers should support some sort of wildcard
header, meaning the key should be present in the headers and can be carrying
any value (key -> void). I am doing it in Python and my question is that
which character is representing this wildcard header?

I have tried *, None, '' and "" and non of them seem to be working. could anyone help me on figuring if this wildcard spec is implemented for header
exchanges in qpid or not.

Thanks,
Siamak



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to