Hi Pavel,
I'm no expert on AMQP, but my suspicion is that this relates to the fact
that the default binding (which is to the default direct exchange) isn't
a "true" binding - as far as I'm aware it is illegal for users to bind
or unbind to the default direct exchange (it's very definitely impossble
to do this via QMF as the address key is <exname>/<qname>/<key> and it
doesnt work with a blank <exname>).
So as a guess because that is essentially a "hardcoded" binding that
can't be unbound etc. I suspect that's why bind events don't get generated.
Someone who knows more about the AMQP spec might be able to give a
better answer though..
Frase
On 03/01/12 10:03, Pavel Moravec wrote:
Hi all,
I realized that currently QMF does not raise an event when a default binding is created (by "default
binding" I mean a binding of type "{exchange:'', queue:<queuename>,
key:<queuename>}" that is created automatically when a queue is created).
To check that behavior, let subscribe to
"qmf.default.topic/agent.ind.event.org_apache_qpid_broker.bind.#" and create a
queue - no message will be send to the subscription. Any other binding crated is notified
by sending a message to the subscription.
My question is: is that a inconsistency that shall be fixed or a desired
behavior?
The answer might not be so plain as the '' exchange and the "default bindings"
are rather hacks to allow sending messages to queues directly. So while technically the
defualt bindings are a real bindings, logically they are not.
Does somebody (plan to) benefit either by raising QMF event when a default
binding is created or not raising so?
Kind regards,
Pavel
---------------------------------------------------------------------
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]
