No, classloaders are isolated too. However do not expect to really *share* code between two service units, as a class loaded from two different SU will be in different classloaders, so they are considered distinct and you can not cast objects (if you use exchange properties for example).
On 12/19/06, moraleslos <[EMAIL PROTECTED]> wrote:
ok. Continuing with this scenario, will I encounter classloader issues if both of my service units happen to package/reference the same lib, e.g. SU 1 and SU 2 both contain commons-net-1.4.1.jar and reference it via <location>lib/commons-net-1.4.1.jar</location>? -los gnodet wrote: > > No, because the spring contexts are isolated. > > On 12/19/06, moraleslos <[EMAIL PROTECTED]> wrote: >> >> Before, when I used different serviceunit ids other than "jbi" in >> servicemix.xml, I ran into exceptions (don't recall the exact exception >> at >> the moment). So I just kept the id name to "jbi". Now if I deploy two >> or >> more serviceunits that all run on top of the lwcontainer component, and >> all >> have their serviceunit ids the same, i.e. "jbi", will there be any >> conflicts? >> >> -los >> -- >> View this message in context: >> http://www.nabble.com/serviceunit-id-question-tf2847958s12049.html#a7953640 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/serviceunit-id-question-tf2847958s12049.html#a7954166 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
