On 10/28/06, bradtwurst <[EMAIL PROTECTED]> wrote:
Thank you. I really do appreciate the help. This participants in this list are top-notch.
Thanks :)
I think that I am starting to understand some of the classloading logic, but I'm sure that I have a boatload of stuff to still learn. Anyway, I did end up including the spring-hibernate (and a few others that are used). That seemed to get me past this concern.
Glad to hear !
As far as deciding whether to include either the full spring jar or not, I don't have the knowledge yet.
I feared that this may cause class incompatibitilies, but I'm not completely sure. So ignore that for the moment.
Thank you all again, James gnodet wrote: > > If you don't use inverse classloading, the hibernate classes > will be loaded from the same classloader than the spring class, > i.e., the container classloader. That's why you have a CNFE. > You can put the hibernate jars in the lib/optional folder. > > The other way is to use inverse classloading, but you may want to > try to include only the spring-hibernate jar instead of the full spring > jar. (maybe we should do that in servicemix, i mean, only including > the spring-core jar instead of the full one). > > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Service-Assembly-with-lightweight-container-not-finding-jars-on-SU-class-tf2521587.html#a7039875 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
