Hi Gordon, To be honest I had no particular reason to unbind from the default exchange, it's just that I'm writing a Java port of qpid-config using QMF2 - and in the process I seem to be going some way to implementing the QMF2 API in Java :-) as part of this I've been trying various scenarios and comparing with the python qpid-config. That was when I noticed that the python one allowed "" as an exchange name and unbound whereas the QMF2 delete binding didn't.
As long as my code is behaving correctly I'm happy :-) Kind of related to this - I've not figured out a way to do "--passive" when adding a queue or exchange with QMF2 it doesn't seem to be one of the properties on create queue. Any ideas on that one? Gordon Sim wrote: > > > Actually its a bug with the exchange.unbind operation. It is illegal to > unbind (or bind) anything from (or to) the default exchange[1]. The > default exchange is a workaround for the fact that up to 0-10 AMQP does > not let you publish direct to a queue. > > Why do you want to unbind from the default exchange? > > > -- View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/QMF2-unbind-doesn-t-seem-to-work-for-default-direct-exchange-tp6592501p6596180.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]
