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 7954 invoked from network); 19 Oct 1999 19:04:14 -0000 Received: from ti34a21-0123.dialup.online.no (HELO tildeslash.com) (130.67.68.123) by apache.org with SMTP; 19 Oct 1999 19:04:14 -0000 Received: (from hauk@localhost) by tildeslash.com (8.9.3/8.9.3) id VAA16858; Tue, 19 Oct 1999 21:10:47 +0200 To: tomcat-dev@jakarta.apache.org Subject: Re: a few comments References: <006501bf1a08$3fe9a300$31b5fea9@paris> <380C8DB8.9718D9D3@mytownnet.com> From: Jan-Henrik Haukeland Date: 19 Oct 1999 21:10:47 +0200 In-Reply-To: "Craig R. McClanahan"'s message of "Tue, 19 Oct 1999 08:26:48 -0700" Message-ID: Lines: 39 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" "Craig R. McClanahan" writes: > > > 2) It would have been great if we could design the Servlet class > > > loader like we have in JSERV1_1DEV so that we can have pluggable > > > ClassLoaders. That way we can (e.g.) have a Java2 classloader that can > > > give servlets loaded a code source, so it's possible to control > > > security permissions for servlets loaded via a Policy file. This is > > > important in a multi hosting servlet environment, for example for ISPs > > > that are hosting servlets. > > > > Yep. Once again, this would be great to see. > > > > Haven't thought about this one at all yet, but agree that it would be great. If you find it interesting, I could try to port the Loader interface and SecureLoader to Tomcat. In addition most of the methods in the current ServletLoader should probably be moved to a LoaderUtil class so that different class loaders can re-use code and use a LoaderUtil class for delegation.