Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2E83F10180 for ; Wed, 5 Feb 2014 19:30:53 +0000 (UTC) Received: (qmail 71869 invoked by uid 500); 5 Feb 2014 19:30:45 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 71798 invoked by uid 500); 5 Feb 2014 19:30:44 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 71739 invoked by uid 99); 5 Feb 2014 19:30:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Feb 2014 19:30:41 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_FILL_THIS_FORM_SHORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of james.strachan@gmail.com designates 209.85.128.181 as permitted sender) Received: from [209.85.128.181] (HELO mail-ve0-f181.google.com) (209.85.128.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Feb 2014 19:30:36 +0000 Received: by mail-ve0-f181.google.com with SMTP id cz12so694766veb.12 for ; Wed, 05 Feb 2014 11:30:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mm+xk8+MMFROaua1C216rOEPe3E+p6dZWHuBasxnHMs=; b=GtyblrgjIHJjTgl5s+qpacxdL4r45nyJ2ax2g8TISxKkVB3MBJ9tUO1qu6HkDbyowt uGI99dSUasS1SLD9N1qEXeZHSZ/AVss6HgeAOH9pgWZCVWthUYRh0oC45/zG3NWHGAj7 EUgvlU9NDEsgXBm1x71MgVMv/gyizuPZFCsc2vbJ6E/AOPBNqut2v1VZlHmQpJHTjh7c p6Yju4R/I1c7MXp1fmx7GzcoxOnkHfiRxqrOlwOSED65hEqZN00eYxG0xbU6xux2s0Pa 1sD4jsMgFegHcRNpOb8tbWwjpO18l4+qOh4vQrzfkmIvXSD9ppnxAOcinOMJJjYXAkjj uWaw== MIME-Version: 1.0 X-Received: by 10.52.236.132 with SMTP id uu4mr948784vdc.47.1391628615012; Wed, 05 Feb 2014 11:30:15 -0800 (PST) Received: by 10.58.186.228 with HTTP; Wed, 5 Feb 2014 11:30:14 -0800 (PST) In-Reply-To: <443BCE38E921434394B45FF0813FA5781ED32139@MSGEXSV21103.ent.wfb.bank.corp> References: <443BCE38E921434394B45FF0813FA5781ED32067@MSGEXSV21103.ent.wfb.bank.corp> <443BCE38E921434394B45FF0813FA5781ED32139@MSGEXSV21103.ent.wfb.bank.corp> Date: Wed, 5 Feb 2014 19:30:14 +0000 Message-ID: Subject: Re: Defining a Queue to a Topic with ActiveMQ From: James Strachan To: "users@activemq.apache.org" Content-Type: multipart/alternative; boundary=089e01183eb441dc3204f1adc921 X-Virus-Checked: Checked by ClamAV on apache.org --089e01183eb441dc3204f1adc921 Content-Type: text/plain; charset=ISO-8859-1 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, 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.strachan@gmail.com ] > Sent: Wednesday, February 05, 2014 2:15 PM > To: users@activemq.apache.org > 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, > > 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: jstracha@redhat.com > Web: http://fusesource.com > Twitter: jstrachan, fusenews > Blog: http://macstrac.blogspot.com/ > > Open Source Integration > -- James ------- Red Hat Email: jstracha@redhat.com Web: http://fusesource.com Twitter: jstrachan, fusenews Blog: http://macstrac.blogspot.com/ Open Source Integration --089e01183eb441dc3204f1adc921--