Hi I got some karaf features fixed that was also wrong, and some due the spring-dm stuff. Also fixed the karaf commands and upgraded so its working again.
The camel-spring-dm module has been merged to master branch and the 9521 branch is deleted. On Wed, Apr 13, 2016 at 4:09 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > I took a stab at ticket > https://issues.apache.org/jira/browse/CAMEL-9521 > > This is only relevant for OSGi users on Karaf / ServiceMix > > > This moves the old spring-dm pieces out of camel-spring into a new > camel-spring-dm module. > > This allows users who are using Camel and install the camel-spring > component to not use spring 3.x JARs anymore. > > So if you have some Camel apps that uses Spring XML on Karaf/SMX then > you need to install camel-spring-dm feature first as it has the > spring-dm pieces (namespace parser extension). > > I pushed this into a new branch 9521 which you can see at > https://github.com/apache/camel/tree/9521 > > The missing pieces is to migrate the osgi related tests in the > tests/camel-itest-osgi to install camel-spring-dm as well. But this > test module is currently not migrated from karaf 2.x to 4.x yet so it > has its own problems. > > To make the maintenance of camel-spring-dm as painless, I moved the > osgi code from camel-spring into this module, and then inlined the > camel-spring into this module,. This was also how it worked before. If > you dont do that you are in for a hell of OSGi classloading hell. > > With the spring-dm out of camel-spring we can also start to make it > deprecated so eventually we can drop it all together. > > The Karaf team is working on a spring xml -> blueprint adapter so you > can write spring xml but it runs as blueprint instead. > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
