On Wed, 2003-09-24 at 19:54, Robert Cauble wrote: > > Multiple classloaders is more restrictive when it comes to > > the security model. Classes in the same package cannot access > > package private methods if the classes are in different classloaders. > > Got it. Thanks. > > > > You can also get errors when instances of the same class name > > but different class objects are passed between classloaders. > > Can you give me an example? Is this something which the JVM can't > handle? Or do mean that it's easy for the programmer to make a mistake > if they were to do something like instantiate an object of a class Foo > loaded from class loader A and then cast it to a class Foo loaded from > class loader B? >
Correct ClassCastException or the more subtle LinkageError, IncompatibleClassChangeError Regards, Adrian > Thanks, > Rob > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Director of Support Back Office JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
