Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

Remove comment about how parent-first loading improves JVM security; it isn't correct.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@371247 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Simon Kitching
2006-01-22 09:17:01 +00:00
parent 8f9d03ad75
commit a52c268a34
1 changed files with 0 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
xdocs/tech.xml
View File

@@ -393,10 +393,6 @@
<p> <p>
Parent-first loading has been the standard mechanism in the JDK Parent-first loading has been the standard mechanism in the JDK
class loader, at least since Java 1.2 introduced hierarchical classloaders. class loader, at least since Java 1.2 introduced hierarchical classloaders.
The primary reason for this is safety -- parent-first
makes it impossible for malicious code to trick the JVM into
replacing a core class (say, <code>java.security.SecurityManager</code>) with a
class of the same name loaded from a child classloader.
</p> </p>
<p> <p>
Child-first classloading has the advantage of helping to improve isolation Child-first classloading has the advantage of helping to improve isolation