Hi Marc:
| taglib details....
No, the taglib needs not be network accessible. Two reasons:
- The URI can use something like "file:/..." protocol,
- The URI can be "well known" to the engine.
| schedule details....
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.
Hope this helps,
- eduard/o
[EMAIL PROTECTED] wrote:
> In section 2.7.7, "The taglib directive," the spec says that the taglib
> directive contains an "uri" attribute where the taglib can be found.
> Does this imply that a taglib must be network-accessible for the JSP
> engine to use it? If so, why? Shouldn't a taglib also be available using
> a "file" attribute containing a relative URL spec, just as in the include
> directive?
>
> I would propose that the taglib directive require either an "uri"
> attribute or a "file" attribute, so that the taglib can be found on the
> filesystem and be consistent with includes.
>
> On page "v", the spec sets out a schedule indicating a late-July release
> of public draft 2, and a mid-August public release. Has public draft 2
> been release? If not, is there an updated schedule available?
>
> 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".
