camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cmoulliard <>
Subject Re: Deploying same camelContext.xml in and out of OSGi
Date Fri, 27 Mar 2009 08:58:06 GMT


We are at the crossroads ("à la croisée des chemins in french"). It will be
very difficult to maintain Camel projects runnable in OSGI and non-OSGI
environments. OSGI projects are really specific because they depends on
bundles, packages must be exported, imported in the MANIFEST file, procedure
deployment and testing ... 
Moreover, the developers/architects will more and more use spring OSGI
facilities like <osgi:service>, <osgi:reference> to expose bundle services
(and use them in another bundle) or <osgix:cm-properties> to pass parameter
coming from properties file. 

So, I cannot figure out how it will be possible possible to run a camel
project in/out of OSGI servers

My feeling is that for the developers, they need a ServiceMix kernel bundle
that we can integrate within Eclipse/NetBeans/... in order to launch our
camel routes and debug them. Temporary, we can use the remote debugging
provided by ServiceMix
to debug our code deployed externally of Eclipse.

In consequence, don't change anything in the existing code.



James.Strachan wrote:
> 2009/3/26 Willem Jiang <>:
>> Adding a Bundle-Activator into the camel-spring module  will introduce
>> the
>> dependency of OSGi jars into camel-spring.
>> I'm wandering if we could do some thing on the camel-osgi module's
>> Bundle-Activator to override the camel-spring's Spring handler?
> Yeah -could we just not have a bundle activator in camel-osgi that
> does the camel-osgi stuff - then delegate (if we need to) to spring-dm
> stuff?
> -- 
> James
> -------
> Open Source Integration

Charles Moulliard
SOA Architect

My Blog :  
View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message