Hi, Still don't understand this issue. We have ignored it up to this point, but now it is becoming more difficult to deal with because we are finding all kinds of other classpath issues, analogous to this one, that can only be resolved by placing all the offending jars in the $SERVICEMIX_HOME/lib/optional directory/. We have played around with many permutations of using the xbean <classpath/> element, inverse="true" attribute, and <hidden/> sub elements.
We have a bit more information about the problem, but still no solution. - org.springframework.aop.config.ConfigBeanDefinitionParser, loaded by a parent classloader of my component classloader, is attempting to load org.aspectj.lang.JoinPoint, which lives in my component classloader. For obvious reasons JoinPoint can't be found because it is in a child classloader. -Seems like a solution could be to hide the above class via <classpath> <hidden>org.springframework.aop.config.ConfigBeanDefinitionParser</hidden> </classpath> -This didn't work. Debugging org.apache.xbean.classloader.MutiParentClassLoader.loadClass(String name), revealed that this method is never called for org.springframework.aop.config.ConfigBeanDefinitionParser. Since it is never called, there is no way for the <hidden>org.springframewor....</hidden> to take effect. -The big question is how is org.springframework.aop.config.ConfigBeanDefinitionParser getting loaded, and by which ClassLoader class. Any help with this issue would be greatly appreciated. Thanks, Brian -- View this message in context: http://www.nabble.com/Spring-AOP-AspectJ-ClassLoader-Issue-tp23031850p24413001.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
