regarding using camel +
activemq in a OSGi environment, without resorting to servicemix?
Maybe these wrinkles are ironed out in camel 2.0?
--
View this message in context:
http://www.nabble.com/Classloading-and-OSGI-tp22303475p22367440.html
Sent from the Camel - Users (activemq
these wrinkles are ironed out in camel 2.0?
--
View this message in context:
http://www.nabble.com/Classloading-and-OSGI-tp22303475p22305791.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
this message in context:
http://www.nabble.com/Classloading-and-OSGI-tp22303475p22309259.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
ObjectHelper will load the class with trying to use the
threadContextClassLoader first.
Since your bundle doen't import the org.apache.camel.component.jms.*.
The threadContextClassLoader which is set to use your bundle classloader
can't see the QueueBrowserStrategy. You will get the
