Optional support in 1.0 is an excellent idea. As with a lot of people on
this list, the non-scripting tags were THE selling point of JSP for me.
Instead of saying something like:
LOOP, EXLUDEIF, INCLUDEIF are postponed until when a Tag
Extension Mechanism is made available...
why not say:
A portable Tag Extension Mechanism will be available in JSP 1.1. The
following extension tags must be implemented in 1.1 compliant servers
<jsp:loop> <jsp:includeif> <jsp:excludeif>. Implementing these tags
(albeit non-portably) is optional for JSP 1.0 servers.
At least then we'll have the stubs to design pages without scriptlet code
all over. In fact, it's not even necessary to define the names or formats
of those three tags. Even this would be fine:
JSP 1.0 compliant servers should implement these three functions ...
These functions will be formalized as part of a Tag Extension
Mechanism in JSP 1.1.
My reasoning here is that it will probably be less intrusive to port from
one extension tag syntax to another than it would be to port from a
scriptlet-based page to a tag-based page. Not to mention making planning
ahead easier.
-Ben
At 09:13 AM 5/7/99 -0500, Mark A. Kolb wrote:
>I predict, however, that as soon as 1.1 becomes available, someone is going
>to write and release a tag library that implements the 0.92 tags (it might
>even be me :). To save much anguish in the meantime, then, I would like to
>suggest that the 1.0 spec include optional support for such a tag library,
>now.
===========================================================================
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".
