David Holmes wrote: > That said, given the check only comes into play when a > security manager is installed, and it may be avoided by a > user-defined classloader, does this actually provide the > protection that was desired?
I'm pretty sure the check *cannot* be circumvented by a user-defined class loader. It may not do the check itself, but that only means it can load a class in another package (that happens to have the same name). For it to load bootstrap classes, it will need to delegate to the system class loader and that's the one doing the checking. Regards, Jeroen _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
