Nick, On 3/1/13 9:29 PM, Nick Williams wrote: > Perusing the Tomcat sources I noticed that there are JSP tag library > XSD files web-jsptaglibrary_1_1.xsd, web-jsptaglibrary_1_2.xsd, > web-jsptaglibrary_2_0.xsd and web-jsptaglibrary_2_1.xsd. However, the > JSP version that Tomcat currently supports is 2.2, and there are > jsp_2_0.xsd, jsp_2_1.xsd and jsp_2_2.xsd files. Does anyone know why > there are is no web-jsptaglibrary_2_2.xsd? I presume because there > were no changes to the tag library XSD between JSP 2.1 and 2.2, but > shouldn't there still be a new version of the XSD regardless (to > match the JSP version)?
Since they would be identical, what's the point? All TLD resolution is done using namespaces, so the namespaces will always resolve to the correct version despite the name of the file(s). Does or offend your sensibilities to not have the "right" file name? > This does not appear to be isolated to Tomcat. A Google search for > "web-jsptaglibrary_2_2.xsd" literally yields zero results (though, > after this email, the result count will undoubtedly increase). That set of filenames is likely to be Tomcat-specific: there's nothing that says that Jetty, JBoss, etc. use web-jsptablibrary_[version].xsd. They may use some other file naming convention. Again, since the resolution is done using namespaces, the names of the files are really irrelevant. -chris
signature.asc
Description: OpenPGP digital signature
