The exchange (broker) does not use the subject at all for it's routing
 as it's not there in AMQP 0-10 (the protocol uses routing key for
this).
The subject was introduced by the new addressing mechanism and is Qpid
specific.
(I believe in AMQP 1.0 the subject is in the protocol itself and
qpid.subject will map directly to that - however I stand to be
corrected).

But for now "qpid.subject" remains a Qpid specific property used by
the new Qpid Client API (and also JMS).
The doc sort of explains how the qpid.subject maps to the AMQP 0-10
protocol - perhaps that section is not clear enough?

Regards,

Rajith

On Fri, Jun 24, 2011 at 10:05 AM, fadams <[email protected]> wrote:
> I'm a bit confused.
> Surely the subject has to have been set *somewhere* by the producer, after
> all I'm successfully subscribing to
> "qmf.default.topic/agent.ind.event.org_apache_qpid_broker.#" so the topic
> exchange would be using the subject to apply the binding.
>
> have I missed something???
>
>
> Rajith Attapattu wrote:
>>
>> Fraser,
>>
>> The client who is sending the message (in this case the QMF component
>> in the broker) is responsible for setting the subject.
>> If receiver side merely retrieves it from the application headers if
>> it's present.
>> So it looks like QMF side is not sending it.
>>
>> I copied Ted on this, as he may be able to give a more definitive
>> answer on that.
>>
>> Regards,
>>
>> Rajith
>>
>>
>
>
> --
> View this message in context: 
> http://apache-qpid-users.2158936.n2.nabble.com/how-do-I-retrieve-the-subject-from-JMS-tp6491033p6512099.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> 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