----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> Tomcat 4 follows the new rules in the servlet 2.3 PFD spec, which allows a
> container to change this so that loading starts with your WEB-INF areas
first.
>
> Consider the following scenario - I put a copy of the Postgres JDBC driver
(just
> to show that it's not specific to xml parsers :-) in my shared library
> directory, because lots of my apps need it. But, one of my webapps needs
a
> different version of the Postgres driver, because it depends on a new
feature
> that was implemented in a later version. So, I put the new driver file in
the
> WEB-INF/lib directory of my webapp, and install it in Tomcat.
>
> Under Tomcat 3.2, the newer driver is ignored (because it's got the same
class
> names). Under Tomcat 4.0, the newer driver is respected for that webap --
all
> others continue to use the shared one.
Craig, I have a small doubt here.
If I place the same jar file containing the class xyz.class in the
tomcat/lib directory and in WEB-INF/lib directory, then will tomcat load the
class from the tomcat/lib directory or WEB-INF/lib directory? If it is
loaded from the WEB-INF/lib directory then this class gets loaded by a
different classloader(webapp class loader) and is incompatible with the
classes loaded from tomcat/lib.
Should the container not check the META-INF/MANIFEST.MF to find out if the
versions are same and if the versions are same it loads the class from
tomcat/lib directory.
Or do the specs mandate that any class in the WEB-INF/lib directory
overrides class found in the tomcat/lib directory.
Do the classes in WEB-INF/lib override the classes on the classpath in
tomcat 4.0?
Regds,
Gokul
>
> Craig McClanahan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
