I have just added following entry to activemq-osgi pom file in current ActiveMQ
master
org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
The problem still exists, but everything looks ok with the wiring:
karaf@root()> exports | grep org.apache.xbean.spring.context.v2
org.apache.xbean.spring.context.v2 | 4.2.0
| 123 | org.apache.xbean.spring
org.apache.xbean.spring.context.v2c | 4.2.0
| 123 | org.apache.xbean.spring
karaf@root()> imports | grep org.apache.xbean.spring.context.v2
org.apache.xbean.spring.context.v2 | [3.13.0,5.0.0)
| resolved | 66 | org.apache.activemq.activemq-osgi
karaf@root()> bundle:classes 123 | grep XBeanNamespaceHandler
org/apache/xbean/spring/context/v2/XBeanNamespaceHandler.class
org/apache/xbean/spring/context/v2/XBeanNamespaceHandlerResolver.class
org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler$1.class
org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler.class
karaf@root()> headers 66
activemq-osgi (66)
------------------
.....
Import-Package =
com.fasterxml.jackson.annotation;resolution:=optional;version="[2.6,3)",
com.fasterxml.jackson.databind;resolution:=optional;version="[2.6,3)",
com.fasterxml.jackson.databind.annotation;resolution:=optional;version="[2.6,3)",
....
org.apache.tools.ant;resolution:=optional,
org.apache.xbean.spring.context;resolution:=optional;version="[3.13,5)",
org.apache.xbean.spring.context.impl;resolution:=optional;version="[3.13,5)",
org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
org.apache.zookeeper;resolution:=optional;version="[3.4,4)",
org.apache.zookeeper.data;resolution:=optional;version="[3.4,4)",
karaf@root()> headers 123
Apache XBean :: Spring (123)
----------------------------
.............
Export-Package =
.......
org.apache.xbean.spring.context.v2;
uses:="org.apache.xbean.spring.context,
org.springframework.beans,
org.springframework.beans.factory,
org.springframework.beans.factory.config,
org.springframework.beans.factory.support,
org.springframework.beans.factory.xml,
org.springframework.context,
org.springframework.core.io,
org.w3c.dom";
version=4.2,
So, the package seems to be correctly exported and wired to activemq-osgi. I
cannot see any other exceptions in log. I tried to refresh/restart/re-resolve
the bundles and the same effect. Altough the package is correctly wired and
contains the necessery class, the class cannot be found in the activemq-osgi
classpath.
One additional observation, maybe it helps - bundle:requirements doesn't show
xbean as requirement for activemq-osgi.
karaf@root()> bundle:requirements 66 | grep org.apache.xbean
karaf@root()>
Kindly regards
Krzysztof
On 27.11.2016 14:09, Jean-Baptiste Onofré wrote:
Hi Krzysztof
yup, it sounds like a missing import.
I gonna take a look later today.
Regards
JB
On 11/27/2016 01:54 PM, Krzysztof Sobkowiak wrote:
Hi
I have tested it yesterday again on Karaf 4.0.7 with Camel 2.17.3 and ActiveMQ
5.14.1 and I can install activemq-broker an activemq-camel. But after restart I
get following error
Caused by: java.lang.ClassNotFoundException:
org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by
org.apache.activemq.activemq-osgi [62]
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
at
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_111]
at
org.springframework.util.ClassUtils.forName(ClassUtils.java:250)[95:org.apache.servicemix.bundles.spring-core:4.2.5.RELEASE_1]
at
org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:125)[89:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1]
I think, addidng import for org.apache.xbean.spring.context.v2 in activemq-osgi
should help (at least as a workaround)
Kindly regards
Krzysztof
On 27.11.2016 12:24, Jean-Baptiste Onofré wrote:
Hi Christian,
Please, ping me tomorrow we can sync/work together on that.
Regards
JB
On 11/27/2016 09:05 AM, Christian Schneider wrote:
My fixes were only touching activemq blueprint. I did not check the
ActiveMQ spring support.
This might be very relevant for TESB though. I will look into it tomorrow.
Christian
2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofré <[email protected]>:
Hi,
Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
Regards
JB
On 11/26/2016 09:44 PM, IODB wrote:
Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
--
View this message in context: http://karaf.922171.n3.nabble.
com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Application Consultant @ Capgemini SSC (http://www.capgeminisoftware.pl/)
