Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 29373 invoked from network); 4 Aug 2009 19:52:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Aug 2009 19:52:39 -0000 Received: (qmail 80221 invoked by uid 500); 4 Aug 2009 19:52:44 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 80177 invoked by uid 500); 4 Aug 2009 19:52:43 -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 80163 invoked by uid 99); 4 Aug 2009 19:52:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 19:52:42 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Aug 2009 19:52:30 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MYQ3N-0001S6-IE for users@activemq.apache.org; Tue, 04 Aug 2009 12:52:09 -0700 Message-ID: <24815070.post@talk.nabble.com> Date: Tue, 4 Aug 2009 12:52:09 -0700 (PDT) From: Joe Fernandez To: users@activemq.apache.org Subject: Re: Virtual Topic and remote Client consumers In-Reply-To: <56b1dfc30908041234t6656382ao762aa538da3a71e1@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: joe.fernandez@ttmsolutions.com References: <56b1dfc30908041234t6656382ao762aa538da3a71e1@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org I believe that by default, the corresponding queue names must follow this syntax=20 Consumer..VirtualTopic. You can override the default naming convention via the element.=20 You might also want to look into using Camel to implement a similar messaging pattern (i.e., recipient list).=20 http://www.enterpriseintegrationpatterns.com/RecipientList.html Joe http://www.ttmsolutions.com =20 Mick Knutson-3 wrote: >=20 > Tell me if this is correct about how to use a Virtual Topic and remote > Client consumers: >=20 > Basically, I create a Virtual topic as a destination for a new Message I > create and send it to: "*jms:VirtualTopic.Table.123*" >=20 > Then by using a remote client running a MDP, I can have each client > subscribe to "*jms:Player.A.VirtualTopic.Table.123*", "* > jms:Player.B.VirtualTopic.Table.123*", > "*jms:Player.C.VirtualTopic.Table.123 > *", etc... >=20 >=20 > This will essentially give me, in AMQ, 1 topic for > *VirtualTopic.Table.123*and then for each client I start, I should be > able to get a message on a > queue "*Player.A.VirtualTopic.Table.123*" ??? >=20 > Just seems like I am missing something on the creation of the Virtual > Topics > and the Queues the consumer(s) connect to. >=20 > Does anyone have examples of this? >=20 >=20 > --- > Thank You=E2=80=A6 >=20 > Mick Knutson, President >=20 > BASE Logic, Inc. > Enterprise Architecture, Design, Mentoring & Agile Consulting > p. (866) BLiNC-411: (254-6241-1) > f. (415) 685-4233 >=20 > Website: http://baselogic.com > Linked IN: http://linkedin.com/in/mickknutson > Vacation Rental: http://tahoe.baselogic.com > --- >=20 >=20 --=20 View this message in context: http://www.nabble.com/Virtual-Topic-and-remot= e-Client-consumers-tp24814828p24815070.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.