You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/11/07 20:08:25 UTC
DO NOT REPLY [Bug 24508] New: -
Webapp class loader issue
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24508>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24508
Webapp class loader issue
Summary: Webapp class loader issue
Product: Tomcat 4
Version: 4.1.27
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: william.lee@cognos.com
The webapp class loading mechanism had been changed from 4.0.x to 4.1.x. In
4.1.x all xerces and xalan classes will be skipped from the webapps directory
(See WebappClassLoader.java).
The problem is that tomcat now forcing every webapps in the same tomcat to use
the same version of xerces and xalan without any choice.
The engineer from Sun pointed out that servlet container should follows the
recommendation defined in the 2.3 specification, and the "endorsed mechansim"
used in JDK 1.4 has nothing to force the webapps to use the "endorsed"
directory. However, after a long discussion in the tomcat developer forum
still getting inconclusive.
Seems to me that a simple "configuration" property will solve all the issues.
Tomcat/webapps should able to be configured to either use the "endorsed"
files, or use the ones from its own "webapps"?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org