2014-01-28 Mark Thomas <ma...@apache.org>:
>> The proposed 6.0.39 release is:
>> [ ] Broken - do not release
>> [X] Stable - go ahead and release as 6.0.39 Stable
>

Ack. Seeing these two issues with Java 5u20 (32-bit, Windows), to be specific.

> Issue 1
> =======
>
> XML validation with DTDs on Java 5 is broken.
>
> Switching to Java 6 fixes this. Given the support status of Java 5 I
> don't plan on addressing this other than mentioning it in the release
> announcement.
>
> For some reason I haven't got to the bottom of, when validation is
> enabled for a web app with a 2.2 DTD the parser attempts to resolve a
> schema with a null public id and null system id. Unsurprisingly this
> fails. The end result is a NPE during parsing which is fatal for a web
> application if it is web.xml that is being parsed.

The same error for 2.3 DTD.

I am testing with test/webapp-(2.2|2.3|2.4|2.5) from trunk.

Confirmed, that placing Xerces 2.11 into CATALINA_HOME/endorsed
fixes this with Java 5.

Webapps start and the following URLs are working:

http://localhost:8080/webapp-2.2/el-as-literal.jsp
http://localhost:8080/webapp-2.3/el-as-literal.jsp
http://localhost:8080/webapp-2.4/el-as-literal.jsp
http://localhost:8080/webapp-2.5/el-as-literal.jsp

> Issue 2
> =======
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=55973
>
> XML validation in Jasper is broken with Java 5. Without r1557719 the
> error in BZ 55973 is displayed. With r1557719, feature not supported
> errors are thrown.
>

I think that I was so happy that with r1561625 the apps started
successfully, that I forgot to test this.

The error is
[[[
SEVERE: Servlet.service() for servlet jsp threw exception
javax.xml.parsers.ParserConfigurationException:
jaxp_feature_not_supported: Feature
"http://xml.org/sax/features/validation"; is not supported.
    at 
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl.setFeature(DocumentBuilderFactoryImpl.java:207)
    at 
org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:115)
]]]

It is odd, because the same feature is set and used in other places.
E.g. it works with Catalina's use of Digester.

I wonder what is the difference.

> Switching to Java 6 fixes this. Given the support status of Java 5 I
> don't plan on addressing this other than mentioning it in the release
> announcement.

OK.

Using Xerces 2.11 fixes this issue as well.

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to