Guillaume Nodet wrote:
I'm working on improving and refactoring the OSGi bits and I'd like to
propose the following:
* make camel-osgi a plain jar just used to share common code between
camel-blueprint and camel-spring
this jar would contain osgi specific classes and also common code for
jaxb parsing / factory logic
both camel-spring and camel-blueprint would embed the classes defined
here as to simplify deployment
Since camel-osgi has a Activactor which has a static Map to hold the
reference of the camel components, type converters, languages etc, I
don't think its a good a idea to embed the Activactor into camel-spring
and camel-blueprint at the same time.
It will cause some trouble when we install camel-spring and
camel-blueprint bundles into the OSGi platform at the same time.
* merge camel-spring-osgi back into camel-spring
this would be easier for end users i think as they would just have to
deploy camel-spring and that's all
whether they are in an osgi environment or not would be transparent
Current camel-spring namespace handler just load the right version
CamelContextFactory by loading the
"org.apache.camel.osgi.CamelContextFactoryBean".
May be we can let it to choice right version of CamelContextFactoryBean
by detecting the OSGi related class.
And this will introduce an OSGi dependency to the people who don't want
to use OSGi.
Thoughts ?
Willem
