A specification is a collection of tradeoffs. Ideally 1.0 would have been
upward compatible with 0.92 but drafts are, by definition, not guaranteed to
be so. In this case we decided that we had to drop some features either to
get the spec out, or to avoid possible conflicts with forthcoming features.
Some people have suggested "adding features in 1.0 even if they change for
1.1". That is not an option. If a feature is added to a release (not to a
draft), the expectation is that it will stay in all "dot" releases after
that [1.1, 1.2, ...]. Unless the feature proves to be a real bug, it will
remain due to upward compatibility.
Some people have suggested using a scriptlet to pass request/response to a
Bean. Besides a (understandable) reluctance by some to use scriptlets, I
have seen no arguments explaining why this is not a workable approach, and I
would also suggest using that in JSP 1.0. A scriptlet, specially one as
idiomatic as this one, is not really that different than a tag.
Hope this helps, and please keep sending feedback!
thanks,
- eduard/o
===========================================================================
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".
