tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher K. St. John" <>
Subject Re: servlet.jar, /ext, MANIFEST.MF
Date Mon, 25 Mar 2002 00:00:17 GMT
Patrick Luby wrote:
> I can't help but think that there might be a way to point Tomcat
> to its bundled jars without losing access to any non-conflicting
> extensions.

 That would be better. (but the servletapi still should have
the appropriate version info :-)

> ... have the class loaders in add the jars in
> the JVM's jre/lib/ext directory to the end of its search list. 

 Hmm. To match the spec, I think there would need to be a new
classloader on top of all of those. Something like:

   ExtClassLoader (pithed)
   AppClassLoader (as normal)
  Catalina /ext   (new: loads /ext classes)
    Common        (as normal)

 Which means that stuff loaded from the classpath won't have
access to extensions, so that's still not quite right. Since
Tomcat closely controls what's on the classpath I'm not sure
how much of an issues that is, but it's definitely a bit
different than normal.

 I'd settle for just having Tomcat print an error message if
there was a conflict, but if the classloader hacks can be
made to work that would obviously be better.

Christopher St. John

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message