2014/1/25 Mark Thomas <ma...@apache.org>:
> I think everything is good to go for 6.0.39. I plan to tag it over the
> weekend with the release vote early next week and (hopefully) the
> release towards the end of the week.
>
Smoke testing with strict servlet compliance = true, without security manager.
Using 32-bit java versions on Win7.
Java 5u20 : fails in a strange way
Java 6u45 : works
The error with 5u20:
[[[
SEVERE: Parse Error at line 862 column 75: src-resolve: Cannot resolve
the name 'javaee:jsp-configType' to a(n) 'type definition' component.
org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name
'javaee:jsp-configType' to a(n) 'type definition' component.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
...
]]]
If strict servlet compliance is disabled, this error does not happen.
A workaround exists:
If I put Apache Xerces 2.11.0 libraries into ${catalina.home}/endorsed, Tomcat
starts working with Java 5u20.
My assessment is that the XML parser in Java 5 is broken and cannot
perform validation.
Maybe it just does not react to the features that we configure.
Unless there are better ideas, I think this can be resolved by putting
a note into Release Notes.
For details:
1. Apache Xerces -Java 2.11.0 can be downloaded here:
http://xerces.apache.org/mirrors.cgi#binary
2. The jars that I put into endorsed directory are
resolver.jar
serializer.jar
xercesImpl.jar
xml-apis.jar
Contents of distributive is described here:
http://xerces.apache.org/xerces2-j/install.html
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
