Hi, Eduardo,
Thanks for the response.
> No, the taglib needs not be network accessible. Two reasons:
>
> - The URI can use something like "file:/..." protocol,
Sure. It just seemed to me that also allowing a "file" attribute (which
the JSP engine would immediately interpret as a file: URI) would make the
syntax consistent with the include directive.
Actaully, wouldn't you also want to make it possible to distribute a
taglib as part of a Web Application (section 1.5)? If so it seems like
specifying the taglib by relative URL would be required by 2.5.2. The
Servlet spec (v2.2), in section 9.2, even explicitly mentions "JSP Bean
and Tags" as possible members of a Web Application. Am I confused about
the relative-url need for .war files (like relative-url specs for .jar
file resources)?
> PD2 has not been released; there is a version of the spec that will go
> for expert review on Monday (tomorrow); the spec will go for public
> review about a week after that, depending on the logistics of pushing
> material to the web site.
Sounds like you're busy -- good luck!
Thanks,
Marc Hedlund <[EMAIL PROTECTED]>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
