Author: skitching
Date: Sun Jan 22 01:17:01 2006
New Revision: 371247
URL: http://svn.apache.org/viewcvs?rev=371247&view=rev
Log:
Remove comment about how parent-first loading improves JVM security; it isn't
correct.
Modified:
jakarta/commons/proper/logging/trunk/xdocs/tech.xml
Modified: jakarta/commons/proper/logging/trunk/xdocs/tech.xml
URL:
http://svn.apache.org/viewcvs/jakarta/commons/proper/logging/trunk/xdocs/tech.xml?rev=371247&r1=371246&r2=371247&view=diff
==============================================================================
--- jakarta/commons/proper/logging/trunk/xdocs/tech.xml (original)
+++ jakarta/commons/proper/logging/trunk/xdocs/tech.xml Sun Jan 22 01:17:01 2006
@@ -393,10 +393,6 @@
<p>
Parent-first loading has been the standard mechanism in the JDK
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>
Child-first classloading has the advantage of helping to improve
isolation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
