On Mar 2, 2013, at 12:48 PM, Christopher Schultz wrote:

> Nick,

Sorry for the delayed reply. I've been sick and was way behind on emails.

> 
> 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).

So it doesn't matter what my XSI schema URL is (web-jsptablibrary_2_1.xsd or 
bark.xsd), as long as the container has some file with a matching namespace URI 
and a matching version. Did I get this correctly?

> 
> Does or offend your sensibilities to not have the "right" file name?

Kind of, yea. I'm OCD. It's a personal problem, I know. I suppose the important 
point is, knowing that the JSP tag library specification is part of the JSP 
specification, regardless of schema URL or anything, I should be able to put 
the current JSP version in the tablib version attribute, but that won't work in 
this case, since the version would be 2.2 but Tomcat 7 doesn't have a 2.2 file, 
just a 2.1 file. There IS technically a JSP tag library 2.2 specification, it 
just doesn't actually differ from the 2.1 specification. So why can't I specify 
version 2.2?

> 
>> 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.

Interesting. I didn't realize that.

> 
> Again, since the resolution is done using namespaces, the names of the
> files are really irrelevant.
> 
> -chris
> 


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

Reply via email to