> I was actually thinking the class would check its own class loader. > So untrusted class loaders could load/define the class, but it wouldn't > work if they did. This check would be "simple" and perhaps more suitable > for initialization code.
I don't follow. The protected class will always get loaded during system initialization by the bootstrap loader. The issue is then to stop application classes from accessing an already loaded class. Hence it is the calling class, attempting to use the already loaded protected class, whose classloader must be checked. David Holmes _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
