Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 69700 invoked from network); 22 Dec 2009 10:07:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Dec 2009 10:07:20 -0000 Received: (qmail 62040 invoked by uid 500); 22 Dec 2009 10:06:27 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 56794 invoked by uid 500); 22 Dec 2009 10:06:12 -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 54947 invoked by uid 99); 22 Dec 2009 09:50:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2009 09:50:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com designates 209.85.211.184 as permitted sender) Received: from [209.85.211.184] (HELO mail-yw0-f184.google.com) (209.85.211.184) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Dec 2009 09:49:57 +0000 Received: by ywh14 with SMTP id 14so5968707ywh.20 for ; Tue, 22 Dec 2009 01:49:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=sYMmEU7NY4FfFh30rgQUlZt4JjFBvyHDxwJ+lpYtOCA=; b=oDuKgk2gOdFyoy+8auzE1r/Ahp4Yzl4vwe1s7QHVvi3V6TJifFkwWZokUJ2sp6M2au rISlorHt0mb/m4bNPxZKU/N+FRzDzHNGnBmDLoiidre7H/r07dstTX7OI+I/nkDoyW9A M6s6f6RQYtfcClgWXN4omU5zt4qnQDi2fSL/4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=fWfush84ToVXIyRHFu3QNt17Kpf80qp1BMVq0KulJQBEaid77EAICOpUERkBilfIlt e/veqiMBo2WXtALPV8nCPI8ffKLvfGn3VG5cBzcSD/3QUZlv0iOeC3IGBwYaRg7up8bv Btha2a/rnQMtQtzlTzmuMU77LyMZchNhzm5Jc= Received: by 10.101.175.37 with SMTP id c37mr2084537anp.102.1261475375929; Tue, 22 Dec 2009 01:49:35 -0800 (PST) Received: from ?192.168.0.158? ([125.33.122.176]) by mx.google.com with ESMTPS id 21sm5370175iwn.6.2009.12.22.01.49.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Dec 2009 01:49:35 -0800 (PST) Message-ID: <4B30962B.9050305@gmail.com> Date: Tue, 22 Dec 2009 17:49:31 +0800 From: Willem Jiang User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: users@camel.apache.org Subject: Re: Sharing a CamelContext across several bundles References: <26885528.post@talk.nabble.com> In-Reply-To: <26885528.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I don't think you get what you want with your pseudo code. As each will create a separate camel context for you, if the endpoint can't be shared in different camel context, you can't access the endpoint from other camel context. For example seda endpoint can only be shared with in same camel context. If you change the bundleB and bundleC to use camel-jms or some other components which can across the different JVM, I think you can get what your want . Willem TheWinch wrote: > Hi everyone, > > Do you know if it is possible to share a single CamelContext across several > bundles ? What I'de like to do is to have several bundles contribute to a > same CamelContext. Example in pseudo code: > >>>From bundle A: define a context > > > > >>>From bundle B: contribute some routes > > > > > > > >>>From bundle C: > > > > > > > > >