I tried again with a simple Camel (just timer and log) jar and kar. In the
feature.xml of my kar file, I have remained only 2 entries:
<feature version="2.15.2">camel-core</feature>
<feature version="2.15.2">camel-spring</feature>
I performed karaf clean and then deploy the jar and kar again, this time the
simple Camel route can be run. I checked again with feature:list |grep
spring... I can see that only spring features of 3.2.14.RELEASE_1 is
started, and so it was able to run. I tried again with the Camel project
with the XSD not found issue, and 4.1.7.RELEASE_1 was used instead
I tried once more using my simple project but add an entry into feature.xml
<feature version="4.1.7.RELEASE_1">spring</feature>
and the XSD not found issue was reproduced.
So 2 questions in my mind:
1) In camel-spring 2.15.x release notes it claimed that Spring 4.1.x is the
default version out of the box, but when I deploy in Karaf it started Spring
3.2.14... was it a Camel feature issue or Karaf issue which choose a
different version (expect 4.1.x, but started 3.1.x) of Spring to run?
2) Does Spring 4.1.7 version not supported in Karaf?
--
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--tp4042748p4042749.html
Sent from the Karaf - User mailing list archive at Nabble.com.
