Yeah; if producer and consumer both use the same kind of destination (both queue or both topic) and they use the same name then there's no need for camel / virtual destinations.
Note in activemq you usually don't need to define queue/topic objects; creating a producer / consumer is enough On Wednesday, February 5, 2014, <barry.barn...@wellsfargo.com> wrote: > So basically you can have a producer put to a topic called Apples, and the > subscriber subscribing to the topic object named Apples, without the need > for the queue object. If you want a topic destination created (queueA or > queueB), you might consider using Camel routes? > > > -----Original Message----- > From: James Strachan [mailto:james.strac...@gmail.com <javascript:;>] > Sent: Wednesday, February 05, 2014 2:15 PM > To: users@activemq.apache.org <javascript:;> > Subject: Re: Defining a Queue to a Topic with ActiveMQ > > A destination is either a queue or a topic. If you want to consume from a > queue/topic and send to a topic/queue the easiest thing is to create a > camel route to bridge them. (There's also virtual destinations in ActiveMQ > which do a similar thing) > http://activemq.apache.org/virtual-destinations.html > > > On 5 February 2014 18:39, <barry.barn...@wellsfargo.com <javascript:;>> > wrote: > > > > > > > In Hawtio, when I define a topic, how do I define a destination queue to > > the topic? Or is that in the hands of the publishing application? > > > > > > > > > -- > James > ------- > Red Hat > > Email: jstra...@redhat.com <javascript:;> > Web: http://fusesource.com > Twitter: jstrachan, fusenews > Blog: http://macstrac.blogspot.com/ > > Open Source Integration > -- James ------- Red Hat Email: jstra...@redhat.com Web: http://fusesource.com Twitter: jstrachan, fusenews Blog: http://macstrac.blogspot.com/ Open Source Integration
