Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B1AF6200B92 for ; Wed, 28 Sep 2016 14:15:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B066D160AD4; Wed, 28 Sep 2016 12:15:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 28E7F160AB4 for ; Wed, 28 Sep 2016 14:15:06 +0200 (CEST) Received: (qmail 32122 invoked by uid 500); 28 Sep 2016 12:15:00 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 32109 invoked by uid 99); 28 Sep 2016 12:14:59 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2016 12:14:59 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7C14DC0CC2 for ; Wed, 28 Sep 2016 12:14:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id G9lJGHY3OSyv for ; Wed, 28 Sep 2016 12:14:57 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 376E25FAF1 for ; Wed, 28 Sep 2016 12:14:57 +0000 (UTC) Received: from static.162.255.23.22.macminivault.com (unknown [162.255.23.22]) by mbob.nabble.com (Postfix) with ESMTP id BC19C323E6A0 for ; Wed, 28 Sep 2016 05:10:49 -0700 (PDT) Date: Wed, 28 Sep 2016 05:14:56 -0700 (MST) From: souciance To: users@camel.apache.org Message-ID: <1475064896132-5788156.post@n5.nabble.com> Subject: camel-rabbitmq multiple bindings/routing keys MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Wed, 28 Sep 2016 12:15:06 -0000 Hello, Does the camel-rabbitmq component support multiple bindings on a queue? That is, can a route consume a rabbit endpoint from(rabbitmq://...) and subscribe to a queue with multiple routing keys? It is supported by standard rabbitmq but wondering if the Camel component supports it as well. Similarly, can you send .to(rabbitmq://..) as producer to multiple routingKeys? Best Souciance -- View this message in context: http://camel.465427.n5.nabble.com/camel-rabbitmq-multiple-bindings-routing-keys-tp5788156.html Sent from the Camel - Users mailing list archive at Nabble.com.