camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Strachan <james.strac...@gmail.com>
Subject Re: Multiple Camel Contexts - why?
Date Wed, 30 Jun 2010 08:35:32 GMT
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/

Mime
View raw message