On 22/01/2014 14:12, Paul Beckett wrote: > Does anyone know: - Why this occurs only since 7.0.50 Changes to XML validation introduced in 7.0.48->7.0.50
- Where the root issue is likely to be / how to fix it Psi probe ships with an implementation of the standard tag library that includes the following: xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee web-jsptaglibrary_2_0.xsd" in a tag library descriptor. The "web-jsptaglibrary_2_0.xsd" is a hint to the location but that is not enough for Tomcat to identify it. Later versions of the standard tag library use: xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; which is unique so Tomcat is able to identify it. One could argue that web-jsptaglibrary_2_0.xsd should be sufficient to identify location of the intended schema. - Are there any significant downsides to turning off tldValidation Only that if there are errors, you won't see them. - The errors don't appear to have stopped things working, can they be safely ignored Yes. Replacing the JSTL implementation in Psi Probe with the one from the examples app should also fix the issue. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
