Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 17648 invoked from network); 27 Feb 2002 22:51:51 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 27 Feb 2002 22:51:51 -0000 Received: (qmail 1514 invoked by uid 97); 27 Feb 2002 22:50:27 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 1467 invoked by uid 97); 27 Feb 2002 22:50:26 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 1395 invoked from network); 27 Feb 2002 22:50:25 -0000 Message-ID: <007f01c1bfe1$316983f0$6501a8c0@apache.org> From: "Remy Maucherat" To: "Tomcat Developers List" References: <001501c1bfc9$52c41b40$1c4da783@wpoliverg> <01b001c1bfce$81b0a450$6501a8c0@apache.org> <00f201c1bfd0$0ba4b150$a0056720@jcarman> <01db01c1bfd0$ceb118a0$6501a8c0@apache.org> <001901c1bfdb$6f886f80$6501a8c0@winxp> Subject: Re: Class Loader Triggers Date: Wed, 27 Feb 2002 14:50:43 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > The documentation states (as you've pointed out) that... > Therefore, from the perspective of a web application, class or resource > loading looks in the following repositories, in this order: > > a.. /WEB-INF/classes of your web application > b.. /WEB-INF/lib/*.jar of your web application > c.. Bootstrap classes of your JVM > d.. System class loader classses (described above) > e.. $CATALINA_HOME/common/classes > f.. $CATALINA_HOME/common/lib/*.jar > g.. $CATALINA_HOME/classes > h.. $CATALINA_HOME/lib/*.jar > Wouldn't it be better to do it this way... > > a.. Bootstrap classes of your JVM > b.. System class loader classses (described above) > c.. /WEB-INF/classes of your web application > d.. /WEB-INF/lib/*.jar of your web application > e.. $CATALINA_HOME/common/classes > f.. $CATALINA_HOME/common/lib/*.jar > g.. $CATALINA_HOME/classes > h.. $CATALINA_HOME/lib/*.jar > I mean, shouldn't the WebappClassLoader first check with the system > classloader, then try to load the classes itself, then go to its parent (the > "shared" classloader)? Wouldn't that solve our little problem with these > "trigger" classes? If this was done, we wouldn't have to worry about > changing the code if Sun decides to include another standard extension in > the core libraries in future versions of the JDK. What do you guys think? I may sound like a broken record here, but you should really look at the latest code, because somehow things may have changed. Thanks for reminding me that I'll need to update the docs, BTW. You still need the some exclusion for JAXP, JNDI (to be safe) and the servlet API, however. Remy -- To unsubscribe, e-mail: For additional commands, e-mail: