2014-01-25 Konstantin Kolinko <knst.koli...@gmail.com>: > 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) > ... > ]]] >
I debugged it to a call to resolveEntity(name, publicId, base, systemId) with the following arguments: name = null publicId = null base = "jar:file:/<redacted>/jsp-api.jar!/javax/servlet/jsp/resources/web-jsptaglibrary_2_0.xsd" systemId = "jar:file:/<redacted>/jsp-api.jar!/javax/servlet/jsp/resources/j2ee_1_4.xsd" The path to j2ee_1_4.xsd is wrong and the file fails to load, thus there are missing definitions. I've proposed a patch for Tomcat 6 to move all copied schema files into servlet/resources directory at compile time. With such a change this issue disappears. I think this is worth applying to Tomcat 7 as well, but I'll wait for tomorrow with that. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
