From qpid-dev-return-10718-apmail-incubator-qpid-dev-archive=incubator.apache.org@incubator.apache.org Fri Jul 04 03:05:23 2008 Return-Path: Delivered-To: apmail-incubator-qpid-dev-archive@locus.apache.org Received: (qmail 59199 invoked from network); 4 Jul 2008 03:05:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jul 2008 03:05:23 -0000 Received: (qmail 36462 invoked by uid 500); 4 Jul 2008 03:05:24 -0000 Delivered-To: apmail-incubator-qpid-dev-archive@incubator.apache.org Received: (qmail 36428 invoked by uid 500); 4 Jul 2008 03:05:24 -0000 Mailing-List: contact qpid-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: qpid-dev@incubator.apache.org Delivered-To: mailing list qpid-dev@incubator.apache.org Received: (qmail 36417 invoked by uid 99); 4 Jul 2008 03:05:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2008 20:05:24 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jul 2008 03:04:41 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 90D61234C14F for ; Thu, 3 Jul 2008 20:04:31 -0700 (PDT) Message-ID: <136477680.1215140671576.JavaMail.jira@brutus> Date: Thu, 3 Jul 2008 20:04:31 -0700 (PDT) From: "Rajith Attapattu (JIRA)" To: qpid-dev@incubator.apache.org Subject: [jira] Resolved: (QPID-803) Add multiple binding keys to a JMS Destination In-Reply-To: <1993246502.1203613399383.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/QPID-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-803. ----------------------------------- Resolution: Fixed I have incorporated all suggestions and this has been tested. Therefore I am going to resolve the issue > Add multiple binding keys to a JMS Destination > ---------------------------------------------- > > Key: QPID-803 > URL: https://issues.apache.org/jira/browse/QPID-803 > Project: Qpid > Issue Type: Improvement > Components: Java Client > Affects Versions: M3 > Reporter: Rajith Attapattu > Fix For: M3 > > Attachments: client.patch, common.patch > > > Currently we can only bind a JMS destination using one key. But there are use cases where you may need to bind a queue using different binding keys to consume messages from different sources. > The JMS Destination provides an abstraction to hide provider details. But from AMQP POV, a JMS destination has a dual nature. > For a producer a destination represents a exchange/routingkey pair. > For a consumer a destination should represent a queue and multiple bindings. > (Ideally it should be an array of the following tuple {exchange,queue,binding}, but this is difficult to express using a simple URL ). > A single destination can be used for publishing, consuming or both, so we need our URL to capture all 3 use cases. > Using the 0-10 protocol we can introduce a bindingKey option that contrains a coma separated binding keys as follows. > Ex: Destination used only for publishing > ------------------------------------------------------ > destination.myQueue = direct://amq.direct//myQueue?routingkey='stock' > Ex: Destination used only for consuming > ------------------------------------------------------- > destination.myQueue = direct://amq.direct//myQueue?bindingkey='car,van' > (This binds a queue to the direct exchange twice using car and van as binding keys) > Ex: Destination used for both consuming and publishing > ------------------------------------------------------------------------------ > destination.myQueue = direct://amq.direct//myQueue?routingKey='vehicle'&bindingkey='car,van' > (This binds a queue to the direct exchange twice using car and van as binding keys for the consumer, and will when the publisher uses it, it will push a message to the direct exchange with the routingKey vehicle) > This has to be backward compatible with old URLs and optimized for the common case where only a routing key is specified. In such a case the routiing key is also used as the binding key -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.