re xml parsing issue, in the server.xml somebody left the useful comment:
<!-- Note: XML Schema validationn will works with Xerces 2.0.1 or
Xerces 2.1. Xerces 2.0.2 and Xerces 2.2 have bugs that prevent
their use with Tomcat-->Because of that I assumed that the bundled xerces would be 2.1 - but I didn't check - unfortunately the tomcat docs only say "Tomcat 5.0 also makes Xerces 2 and the Commons Logging API (release 1.0.3)
available to web applications."
I'm a bit ashamed to ask, but is there any way of telling what version the jar file is, from the jar itself?
The following recent mail on tomcat-dev explains the issue.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg47251.html
I'll see whether I can find the old version of xerces and install that, which should make the issue disappear. Or crimson.
Adam
On 10/03/2003 09:30 AM Hans Bergsten wrote:
Re: the tomcat start-up exceptions
preRegister with Catalina:type=Logger,path=/blacksail,host=localhost
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content starting with element 'jsp-version'. The content must match
'((("http://java.sun.com/xml/ns/j2ee":description){0-UNBOUNDED},("http://java.sun.com/xml/ns/j2ee":display-name){0-UNBOUNDED},("http://java.sun.com/xml/ns/j2ee":icon){0-UNBOUNDED}),("http://java.sun.com/xml/ns/j2ee":tlib-version),("http://java.sun.com/xml/ns/j2ee":short-name),("http://java.sun.com/xml/ns/j2ee":uri){0-1},("http://java.sun.com/xml/ns/j2ee":validator){0-1},("http://java.sun.com/xml/ns/j2ee":listener){0-UNBOUNDED},("http://java.sun.com/xml/ns/j2ee":tag){0-UNBOUNDED},("http://java.sun.com/xml/ns/j2ee":tag-file){0-UNBOUNDED},("http://java.sun.com/xml/ns/j2ee":function){0-UNBOUNDED},("http://java.sun.com/xml/ns/j2ee":taglib-extension){0-UNBOUNDED})'.
This is some sort of xml parsing problem, I've narrowed it down to the following declaration in tomcat's server.xml:
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="true" xmlNamespaceAware="true">
When I remove the xmlValidation & xmlNamespaceAware attributes, the startup exceptions disappear. I put these attributes in as true so that tomcat would catch any errors I make in the server.xml. Obviously I can live without it or even live with the errors, but it's not happy.
And the exceptions only occur on startup if I delete the tld caches.
It seems this is an issue with jakarta-taglibs and tomcat, rather than with my configuration. Is that so?
I've seen some messages on the Tomcat Developers list about problems with XML Schema validation due to bugs in the bundled version of Xerces. If you absolutely need the validation, you may want to try to replace it with a different JAXP compliant XML parser that handles XML Schema validation.
Hans
-- struts 1.1 + tomcat 5.0.12 + java 1.4.2 Linux 2.4.20 RH9
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
