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 778C47FFB for ; Mon, 1 Aug 2011 15:22:14 +0000 (UTC) Received: (qmail 76623 invoked by uid 500); 1 Aug 2011 15:22:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 76496 invoked by uid 500); 1 Aug 2011 15:22:13 -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 76488 invoked by uid 99); 1 Aug 2011 15:22:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2011 15:22:13 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chubrilo@gmail.com designates 209.85.161.43 as permitted sender) Received: from [209.85.161.43] (HELO mail-fx0-f43.google.com) (209.85.161.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2011 15:22:07 +0000 Received: by fxg17 with SMTP id 17so6177885fxg.2 for ; Mon, 01 Aug 2011 08:21:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=VuTUhoIscimO3q3R9+O9phO2XacsXUjKaIvLwwkexHw=; b=tJJrAxhNG2SUXV+37sVexN3VDrfNfTQAdyICrKVTC25IZcmUeK8JueywS3vu8vwn5u D2JWC9FAnDm8BZbmeyWZ/xfRKKvCKSAHx/fK8UORGwSsRn5BXuOEEG/ZPbu05Z8NyjFM +LUt75BESpgZ/XgiJqu4InUcPkvLEsaHddCPY= MIME-Version: 1.0 Received: by 10.223.155.74 with SMTP id r10mr705594faw.32.1312212106816; Mon, 01 Aug 2011 08:21:46 -0700 (PDT) Sender: chubrilo@gmail.com Received: by 10.223.96.142 with HTTP; Mon, 1 Aug 2011 08:21:46 -0700 (PDT) In-Reply-To: <1312202092176-3709528.post@n4.nabble.com> References: <1312202092176-3709528.post@n4.nabble.com> Date: Mon, 1 Aug 2011 17:21:46 +0200 X-Google-Sender-Auth: 0VCb8Vl6lwE38h0uYGbcEwk0nGg Message-ID: Subject: Re: Wildcards From: Dejan Bosanac To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=00235400f4367f2c3f04a97330ab X-Virus-Checked: Checked by ClamAV on apache.org --00235400f4367f2c3f04a97330ab Content-Type: text/plain; charset=ISO-8859-1 Maybe a better solution for your application would be to use composite destinations. So producer 1 will send messages to A,B,C,D,E, producer 2 to A,F,G,H and a subscriber would simply listen on topic A. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Mon, Aug 1, 2011 at 2:34 PM, mcamnadur wrote: > Hi > > I am trying to use ActiveMQ's Wildcard capability with respect to > subscription to the different topics. Now, I wish to implement an > architecture where the producer would publish to a topic containing a > number > of keywords (seperated by '.'). The client would subscribe to any > topic/queue containing the requested keyword. In other words rather than > using a hierarchical approach we will use a 'tag' approach. For example, > Producer_1 would write to A.B.C.D.E while Producer_2 would write to > A.F.G.H: > Then if client 1 would subscribe to >.A.> he would receive from both > Producer 1 and 2...however, this feature does not appear to be working, > instead, the client is subscribing to ALL topics. Is there a fix for this? > > Thanks > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Wildcards-tp3709528p3709528.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --00235400f4367f2c3f04a97330ab--