This suggests that another option is to simply leave xerces (and possibly xalan) out of the mmbase web-app deployment. It simply uses the XML parser that TomCat makes available, which is probably fine. I prefer this solution over forcing an XML parser onto all other webapps that may be deployed.
Rob van Maris Developer Finalist IT Group Java Specialists ------------------------------------------------------------- Amsterdam, The Netherlands Office: +31 20 5962321 (Direct) Mobile: +31 651444006 Fax: +31 20 5962331 ------------------------------------------------------------- ----- Original Message ----- From: "Kees Jongenburger" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 28, 2002 10:17 AM Subject: Re: mmbase-src-1.6.0-rc1 > True, the release notes should mention that. > I heard something similar is true for tomcat but I am not sure (can > someone verify?). this is true. from the relase note of tomcat RELEASE-NOTES-4.1.txt -------------------------- Tomcat 4.1 and XML Parsers: -------------------------- As described above, Tomcat 4.1 makes an XML parser (and many other standard APIs) available to web applications. This parser is also used internally to parse web.xml files and the server.xml configuration file. If you wish, you may replace the "xercesImpl.jar" file in "common/endorsed" with another XML parser, as long as it is compatible with the JAXP 1.1 APIs.
