The purpose is that classes in SU are for use in SU and shouldn't conflict with classes in other SU for the same SE (or any other SU), e.g. you may have two different SUs for bean component, both using Hibernate jars but in different versions. Classes in SE are used for SE implementation itself. But I can't explain why some of them are visible in SU and some not (I recall that JBI specification says something about hierarchy of classloaders in SE/SU so you may check there as well)
Ryan Moquin wrote: > > Out of curiousity, what purpose do the classes in the lib directory of a > service engine perform compared to the classes in the lib directory of a > service unit? What jars should be in which? I'm seeing some odd stuff > where some classes are being found when starting my service unit which are > contained in a jar in my service engine, but other classes are said to not > be found by the service unit that are in the same jar file in the service > enginer as the other classes that were found. Which seems odd. I don't > have any problems deploying a service unit onto the service engine in an > servicemix from a unit test. I'm a little puzzled on how this > classloading > works in a the standalone servicemix and tomcat servicemix. > > Thanks for any help! > > Ryan > > -- View this message in context: http://www.nabble.com/Classloading-for-service-engine-vs.-service-unit-tp21670762p21681609.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
