It's possible that the same class might be used:
a: Internally by the servlet engine itself (Say Orion or Tomcat)
b: By the servlet developer (me, the application developer)
In my case I want to use an xml library (the latest jaxp from Sun) but Orion
already has an xml library (an older version of same) that it uses
internally. What's more, Orion's internally used xml library has the exact
same class/package names as the newer one I whant to use.
Thus, Orion's internal xml library (the older one) is taking precedence over
the one I have installed in my web-app's lib folder.
Here are the two "quasi-solutions" I have come up with:
1. For Tomcat, simply use the newest version tomcat 4 beta, which internally
uses the newest version of JAXP.
2. For Orion, modify orion.jar's manifest file to force Orion internally to
use the newer xml library.
Both of these seem like hacks and do not guarantee the portability of my
web-app.
Q1: Is there anything in the servlet spec that addresses this issue?
Q2: Anyone know of a more elegant, portable solution?
If not, it seems to me that the servlet spec should be modified to require
that classes used internally by the servlet engine should be in a separate
name space (classloader?) from those used by the servlet/web-app developer
(i.e. in the WEB-INF/classes and WEB-INF/lib) folder.
Thanks,
Dave Ford
Smart Soft - The Java Training Company
http://www.smart-soft.com
___________________________________________________________________________
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
