Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of james.strachan@gmail.com
 designates 72.14.220.156 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=qsZfjjLEpqR3o6qrkAx8vrqiJwUNkQBeAm/4v2IOYmnsJYFxJ5A8U0L2MUV09UzLgP
         XKsD5s1iPMFI2kvJcIbo3vcYIiG5GeM0hc6od1I53NTcnwq8pPRu1f4A4pyCBssCqMbR
         MoRzeXkntMH7nZWBz74iLcdKOoySg/YvUpFMk=
MIME-Version: 1.0
In-Reply-To: <4C2B0127.8070001@progress.com>
References: <1277886296374-512038.post@n5.nabble.com>
 <4C2B0127.8070001@progress.com>
From: James Strachan <james.strachan@gmail.com>
Date: Wed, 30 Jun 2010 09:35:32 +0100
Message-ID: <AANLkTinVZRHbPicChngdRHLVFlLrRjZ-oAchwvDCR8Xm@mail.gmail.com>
Subject: Re: Multiple Camel Contexts - why?
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 30 June 2010 09:32, Adrian Trenaman <trenaman@progress.com> wrote:
> Hi Gallapagus,
>
> In general, you don't tend to want multiple camel contexts in your
> application, if you're running Camel as a standalone Java instance. However,
> if you're deploying Camel routes as OSGi bundles, or WARs in an application
> server, then you can end up having multiple routes being deployed, each in
> it's own, isolated camel context, in the same JVM. This makes sense: you
> want each Camel application to be deployable in isolation, in it's own
> Application Context, and not affected by the other Camel applications.
>
> If you want the endpoints or producers in different camel contexts to
> communicate with another, there are a number of solutions. You can use the
> ServiceMix NMR, or you can use JMS, or you can use Camel's vm transport.

Agreed - one minor nit - the vm transport, only works if Camel is on a
shared class loader across deployment units. So that won't work in
WARs unless camel is on your system classpath & will only work in OSGi
if you are reusing the same version of camel across your bundles.


-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/