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
* 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
Thoughts ?
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
