It is a "bug" in PR1. We will fix it.
- eduard/o
(sorry for being terse, I'm in a hurry)
"Craig R. McClanahan" wrote:
>
> In looking through the JSP 1.1pr specification, I could not find any
> description of a standard deployment format for tag extensions and their
> associated tag library descriptor (TLD) files. It is also not clear
> exactly what the "tagLibraryURI" (Section 2.7.7.1) in the taglib
> directive actually points at - is it a TLD file, a JAR file, a
> directory, or what?
>
> I would have expected to see a defined JAR file format for tag extension
> libraries, with the TLD file at a specified name in the META-INF or
> WEB-INF directories inside the JAR -- reminiscent of the way that the
> Servlet 2.2 spec defines the "web application archive" for deployment.
> If this were done, I would expect that the tag library URI would point
> at either the deployment file itself, or an "unpacked" directory
> structure organized the same way, or some such similar mechanism.
>
> Without a standard deployment format for tag extensions, it would seem
> that tag libraries would have to be packaged for each JSP implementation
> specifically, which hardly seems like a desirable approach.
>
> Craig McClanahan
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
