Duane Morse wrote:
>
> Is there a standard way to change the CLASSPATH seen by
> servlets so this sort of conflict can be avoided?
>
The 2.3 spec:
<URL:http://java.sun.com/products/servlet/download.html>
says:
9.6.2 Web Application Classloader
The classloader that a container uses to load a
servlet in a WAR must not allow the WAR to override
JDK or Java Servlet API classes, and is recommended
not to allow Servlets in the WAR visibility of the web
containers implementation classes.
If a web container has a mechanism for exposing
container-wide library JARs to application
classloaders, it is recommended that the application
classloader be implemented in such a way that classes
packaged within the WAR are able to override classes
residing in container-wide library JARs.
Which probably doesn't do you much good right at the
moment, since 2.3 isn't finalized yet. It offers some
hope for the future, though. The theory would be that
you'd dump your jar into the appropriate WEB-INF directory,
and things would work as you expect. The 2.3 spec has
quite a bit more detail on things like that, including
how to declare dependencies on container-wide classes,
it's worth a read.
-cks
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
