Hi,
After doing some tests on the trunk version of servicemix4, I found the
osgi example work perfectly with the camel-spring target namespace.
I checked the osgi bundles , and found that it just a simple change
which was made by Guillaume.
He just let the kernel to load camel-osgi bundle before
ource.com/
>
>
-
Charles Moulliard
SOA Architect
My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
--
View this message in context:
http://www.nabble.com/Deploying-same-camelContext.xml-in-and-out-of-OSGi-tp22684580p22737964.html
Sent from the Camel - Users mailing list archive at Nabble.com.
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 j
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?
Willem
On Thu, Mar 26, 2009 at 5:14 PM, Gert V
Sounds like a good idea - assuming that the bundle activator kicks in
before Spring DM processes the XML?
2009/3/26 Gert Vanthienen :
> Willem,
>
> Would adding a Bundle-Activator to our jars help? The activator would
> only be called upon in an OSGi environment so it could take of putting
> in p
Willem,
Would adding a Bundle-Activator to our jars help? The activator would
only be called upon in an OSGi environment so it could take of putting
in place everything that's necessary for OSGi without the need for
anyone to change the configuration in the XML files.
Regards,
Gert Vanthienen
-
Hi,
Yes, in servicemix-camel component, we can use the Spring namespace for
OSGi and non-OSGi environment. That is because ServiceMix take charge of
the Camel Spring handler itself, and the Spring handler of camel-spring
will detect the CamelContextFactoryBean of OSGi (in the camel-osgi
bundle) by
BTW I remember having a chat with Guillaume a while back and I don't
think the OSGi namespace in the XML is required any more; I think he
figured out how to wire in the OSGi injection without having to change
the XML namespace. Though I've not tested it to be sure though - want
to give it a try?
T
Hi Aaron
The CamelContextFactoryBean of OSGi version extends the
CamelContextFactoryBean of Spring version. It only add the handle of
bundle context injection. For non-OSGi container it will not inject the
bundle context into the OSGi CamelContextFactoryBean, so the OSGi
CamelContextFactoryBean w
I have the following XML I'd like to deploy both in an OSGi container, and a
non-OSGi container. To deploy in the OSGi container, I have to use the
"osgi" schema so that the "quartz" component is resolved to the camel-quartz
bundle.
To deploy in a non-OSGi container, I had to add spring-osgi-core
10 matches
Mail list logo
