Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 59080 invoked from network); 25 Jan 2001 23:35:46 -0000 Received: from patan.sun.com (192.18.98.43) by h31.sny.collab.net with SMTP; 25 Jan 2001 23:35:46 -0000 Received: from shorter.eng.sun.com ([129.144.252.35]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA16541 for ; Thu, 25 Jan 2001 15:35:53 -0800 (PST) Received: from eng.sun.com (d-ucup02-251-111 [129.144.251.111]) by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.0) with ESMTP id PAA13459 for ; Thu, 25 Jan 2001 15:35:52 -0800 (PST) Message-ID: <3A70BA6F.782B2F8B@eng.sun.com> Date: Thu, 25 Jan 2001 15:44:47 -0800 From: Anil Vijendran X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: Tomcat 4 Jasper ClassLoading changes to support SecurityManager References: <3A70ACBC.C3C6E99B@voyager.apg.more.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N +1. Glenn Nielsen wrote: > In order to make it easier to integrate the SecurityManager into Jasper > for Tomcat 4 and to change some of Japsers annoying behaviours, I have > been working on switching Jasper over to the URLClassLoader. > > I have the class loading changes in place and Jasper passes all watchdog > tests. I wanted to run these changes past everyone before I finish > cleaning up the changes and committing it. (I still have some work to > do on JspC and still need to add support for the SecurityManager.) > > Jasper now creates a URLClassLoader for each JSP page and defers any other > class loading to the web app context class loader. Using a single class > loader per JSP allowed me to remove all the code that increments the > class version number, i.e. the work directory no longer has multiple > *.java and *.class files for the same JSP page. These changes also made > it easy for me to put the java source and class files in the same directory > tree as found in the web app context. When Jasper is run in a servlet > container it no longer puts the class files in a package, they are now > in the default package. > > These changes simplified the code quite a bit and also gave a performance > improvement. > > When running watchdog tests the new jasper was ~25% faster than the current > jasper on a first compile or on first jsp class access after restart. > On recompile of a jsp page it was 37% faster. Execution of JSP servlet > after it had already been compiled and loaded was slightly faster. > > Regards, > > Glenn > > ---------------------------------------------------------------------- > Glenn Nielsen glenn@more.net | /* Spelin donut madder | > MOREnet System Programming | * if iz ina coment. | > Missouri Research and Education Network | */ | > ---------------------------------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org > For additional commands, email: tomcat-dev-help@jakarta.apache.org -- Peace, Anil +<:-)