From a52c268a343044a3ba33018443df96fa921a1083 Mon Sep 17 00:00:00 2001
From: Simon Kitching <skitching@apache.org>
Date: Sun, 22 Jan 2006 09:17:01 +0000
Subject: [PATCH] Remove comment about how parent-first loading improves JVM
 security; it isn't correct.

git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@371247 13f79535-47bb-0310-9956-ffa450edef68
---
 xdocs/tech.xml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/xdocs/tech.xml b/xdocs/tech.xml
index a15ce26..6b0e42b 100644
--- a/xdocs/tech.xml
+++ b/xdocs/tech.xml
@@ -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