One very important thing is that you must avoid to mix different spring
versions at runtime.
Christian
On 24.09.2015 15:16, xlogger wrote:
Finally able to dig out the issue after some tries... it is because of below
entry in feature.xml:
<feature version="4.1.7.RELEASE_1">spring-jms</feature>
The issue is fixed after changing the version to 4.2.0.RELEASE_1
But it's really strange to me that an issue on particular spring-jms feature
version would introduce such XSD exception...
--
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--tp4042748p4042752.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
