camel-spring and camel-blueprint embed the OsgiDefaultCamelContext in
their bundle to avoid the bundle start sequence issue.
If you want to use the OsgiDefaultCamelContext, you may consider to use
the camel-core-osgi bundle directly.
On Tue Nov 1 23:19:44 2011, Raman Gupta wrote:
I've played with this a bit more... things seem to work much better
when the camel context and routes are in the same bundle. Then one can
simply start the context on bundle activation and stop on
de-activation, and the associated routes (autostart=true) are
started/stopped along with the context. The way I was trying required
coordination of context/route stops/starts across bundles via
listeners, and getting all the context/route/bundle state combinations
and transitions working.
However, now I have one context per bundle using Camel. Would there be
significant overhead to having several (8-10) Camel contexts running
within the JVM at once?
On a related note, I used
org.apache.camel.core.osgi.OsgiDefaultCamelContext to get this
working. This class appears to be in two bundles, but both have small
issues in camel 2.8.2:
camel-core-osgi (but this is not included in the camel features.xml)
camel-spring (but the org.apache.camel.core.osgi package is not exported)
I see that OsgiDefaultCamelContext has been removed from camel-spring
on trunk, but camel-core-osgi is still not listed in features.xml.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
