Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 54216 invoked from network); 5 Dec 2009 09:31:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Dec 2009 09:31:39 -0000 Received: (qmail 89777 invoked by uid 500); 5 Dec 2009 09:31:39 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 89729 invoked by uid 500); 5 Dec 2009 09:31:39 -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 89719 invoked by uid 99); 5 Dec 2009 09:31:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Dec 2009 09:31:39 +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; Sat, 05 Dec 2009 09:31:29 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NGqyq-0004Oo-B1 for users@camel.apache.org; Sat, 05 Dec 2009 01:31:08 -0800 Message-ID: <26654086.post@talk.nabble.com> Date: Sat, 5 Dec 2009 01:31:08 -0800 (PST) From: Hendy Irawan To: users@camel.apache.org Subject: Implementing Publish Subscribe Channel MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: hendy@soluvas.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I was trying to make a publish-subscribe mechanism by using (only) @EndpointInject and @Consume, so that I can have somewhat POJO style routing with minimal XML configuration. It turned out that this didn't work because multiple consumers don't work with this setup. After reading http://camel.apache.org/publish-subscribe-channel.html it seems that there are only three ways Camel supports Publish Subscribe: 1. JMS Topic 2. XMPP Room 3. Explicit routes via multicast Option 1 and 2 is overkill because it requires external server. So the functionality is basically there in Camel (option 3), however, I cannot do it dynamically because it involves explicitly setting up the routes, instead of doing it dynamically via @Consume. Spring Integration seem to support this by allowing to create a PublishSubscribeChannel explicitly. Is it planned to support easy "dynamic" Publish Subscribe Channel via annotations (i.e. without explicit configuration)? Thank you. -- View this message in context: http://old.nabble.com/Implementing-Publish-Subscribe-Channel-tp26654086p26654086.html Sent from the Camel - Users mailing list archive at Nabble.com.