> When the servlet container and your own servlets use a common package,
> there's a potential
> for a version conflict. I've encountered this with Tomcat and the JRun.
> The "early access" XML API
> from Sun which we used was incompatible with the XML API Tomcat and JRun
> came with --
> in particular, the servlet container said it couldn't find method
> getXMLReader in
> javax.xml.parsers.SAXParser -- the jar file that Tomcat and JRun used
> contained an early version of
> SAXParser that didn't have this method.
>
> Is there a standard way to change the CLASSPATH seen by servlets so this
> sort of conflict
> can be avoided?
Unfortunately, no. Finding class files is container specific. And
confusing, too, since most containers do more than just the CLASSPATH in
order to support hot deployment.
You could seal the packages in your jar files. This won't solve the
problem, but it will detect it (by triggering an exception).
Stuart Halloway
DevelopMentor
http://staff.develop.com/halloway
___________________________________________________________________________
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
