Hi Christian,
I tried to test with a simple Camel project (only a timer and then log) and
included 2 entries to feature.xml only
<feature version="2.15.2">camel-core</feature>
<feature version="2.15.2">camel-spring</feature>
After I deploy my application and perform feature:list |grep spring, I found
that the feature spring/3.2.14.RELEASE_1 was started. I tried to add one
more entry like <feature version="4.2.0.RELEASE_1">spring</feature> to
feature.xml and redeploy, and both 3.2 and 4.2 spring versions are
started...
Is it possible to enforce camel-spring feature to start with spring 4.2
instead?
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-4-0-1-Unable-to-locate-Spring-NamespaceHandler-for-XML-schema-namespace-http-camel-apache-org--tp4042748p4042754.html
Sent from the Karaf - User mailing list archive at Nabble.com.
