Hi

I've seen this problem brushed upon in a few previous posts, but never
actually resolved as far as I can tell. As the title suggests, I can't
persuade a Camel service-unit to load its own classes. Specifically,
Servicemix is providing old versions of spring-core and spring-beans and
loading dependencies from them before my SU gets a chance to, with tedious
NoSuchMethodError results. I've tried with various versions of Servicemix
3.2.x and 3.3.x to no avail, and as many versions of Camel as I can eat.
Whatever configuration of dependencies I use in Maven, nothing works. I've
unpacked every SU to see if the rogue jars are there, and they're not. I'm
sure this is a classloading problem, but I have no idea how to solve it. 

Anybody got any ideas? Moving to Servicemix 4 is not an option

thanks for looking
-- 
View this message in context: 
http://old.nabble.com/How-do-I-force-self-first-classloading-in-Camel-SU--tp28809688p28809688.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to