Hi Stepan, Queues are automatically bound to the direct exchange by default at creation time, and the JMS destination name will be used to route messages to the queue using a MessageProducer, and also for consuming from the queue.
For topics, you can filter using the message selector on creation of the topic subscription using JMS apis - which under the covers means that only messages matching your selector are delivering into the subscriber's private queue for consumption. Hope that sheds some light ? Only in unusual situations would you want to create the bindings between a queue and an exchange manually, usually applications wish to consume round robin from a topic - for example. Let us know if you need to do something unusual and we'll advise ? Hth, Marnie On Thu, Feb 17, 2011 at 12:03 PM, stepik <[email protected]>wrote: > > Hi Marnie, > > thanks a lot for a quick answer. I have another: What about if I needed a > direct exchange instead of topic? Or if I needed topic with filtering the > messages depending on their routing keys...I mean how can I specify the > binding between exchange and queue in virtualhosts.xml file? > > Regards, > > Stepan > > -- > View this message in context: > http://apache-qpid-users.2158936.n2.nabble.com/problem-with-binding-in-virtualhosts-xml-for-JAVA-broker-tp6035027p6035616.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] > >
