Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-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 EA52CE685 for ; Fri, 15 Mar 2013 13:00:24 +0000 (UTC) Received: (qmail 6504 invoked by uid 500); 15 Mar 2013 13:00:24 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 6357 invoked by uid 500); 15 Mar 2013 13:00:24 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 6338 invoked by uid 99); 15 Mar 2013 13:00:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 13:00:24 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gsim@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 13:00:17 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r2FCxtLS011594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 15 Mar 2013 08:59:55 -0400 Received: from [10.36.116.66] (ovpn-116-66.ams2.redhat.com [10.36.116.66]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r2FCxsio008283 for ; Fri, 15 Mar 2013 08:59:55 -0400 Message-ID: <51431C48.8000000@redhat.com> Date: Fri, 15 Mar 2013 13:04:08 +0000 From: Gordon Sim Organization: Red Hat UK Ltd, Registered in England and Wales under Company Registration No. 3798903, Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parsons (USA), Charlie Peters (USA) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: Using QPID AMQP via SwiftMQ Java API References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.25 X-Virus-Checked: Checked by ClamAV on apache.org On 03/15/2013 01:22 AM, Jason Barto wrote: > I'm new to AMQP 1.0, coming from RabbitMQ/9-1 and I am trying to get my > head wrapped around the changes. I'm creating an AMQP test client using > SwiftMQ's Java API. Which broker are you working with? (The java broker or the c++ broker?) > I have a producer sending messages to a topic with a specific subject (I > understand these are aligned with the old routing keys?). Correct. > Where I'm confused is how to create a consumer for messages sent to the > topic with a specific subject. The SwiftMQ API doesn't permit for > specification of anything other than a source with an optional 'message > selector' (I think that's a JMS term?). Do I need to specify a message > selector in order to get my consumer bound to a topic with a particular > routing key? Or is this done through the source address? A JMS selector filter will not currently work as expected with the c++ broker. Support for selectors is being added but it does not yet cover the case where a consuming link is established to a topic exchange. There is support for a subject filter (https://svn.apache.org/repos/asf/qpid/trunk/qpid/specs/apache-filters.xml#type-legacy-amqp-topic-binding) but that is a registered extension to the core protocol (as is the selector filter) and is likely not supported by the SwiftMQ client. Andreas could probably clarify that. I'm not sure of the situation with the java broker. Rob, will a selector on its own work as expected when creating a link from a topic exchange? Or perhaps using a fanout exchange since the selection is done entirely by the selector? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org