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=3809>. 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=3809 Jar files in the wrong directories. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2001-10-01 13:04 ------- Here's the current status my recommendations on dealing with the several issues raised in this bug report: * Should Tomcat 4 expose an XML parser by default to web apps? (Tomcat 3.2 does. All J2EE servers do. Lack of this causes lots of newbie user problems). Recommendation: Yes * Which parser should be exposed by default? Recommendation: Xerces 1.4.3 (this is implemented in the current CVS code, and seems to solve all of the sealing violation and class cast exception problems caused by JAXP) Note: The release notes will tell you how to undo this if you don't want to - but we're talking about *defaults*. * What about problems caused by "jndi.jar"? Recommendation: Fixed in most recent CVS code. This JAR file will not be included in the class loader on JDK 1.3 or later systems where it's already integrated into the JDK. * What about problems caused by "ldap.jar"? Recommendation: Remove from the build. It only affects JDK 1.2.2 users that want to use JNDIRealm. NOTE: Conditional inclusion fix for jndi.jar works for this (and for several other libraries that have been included in JDK 1.4). Bottom line - I believe that all of the issues raised by this bug report have been addressed in current CVS code that will be included in 4.0.1. I will close the bug report on that basis. Anyone who still has a problem with *CURRENT CVS CODE* on the "tomcat_40_branch" branch can reopen it.
