On Fri, 2003-03-21 at 11:08, Shawn Bayern wrote:
> JSP 2.0 (for which standard Tomcat 5.0 is a compliant container) shifts
> the responsibility of evaluating EL expressions to the container, not
> individual tag handlers. If you're writing an application for JSP 1.2,
> you could theoretically use our ExpressionEvaluatorManager to parse
> expressions from anywhere, including BodyContent; simply ignore the
> arguments associated with tag attributes.
>
> Note that without JSP 2.0's support, retrieving expressions from
> BodyContent and parsing them at doEndTag() (or some other fixed point) can
> be extraordinarily confusing to users. Consider the following situation:
>
> <my:tag>
> ${a}
> <c:set var="a" value="${...}" />
> </my:tag>
>
> The user will probably expect ${a} to evaluate to its original value, but
> if the tag's only opportunity to read and parse the content comes within
> doEndTag(), ${a}'s evaluation will be affected by the <c:set> that occurs
> *after* its presence in the page.
So... to me this implies that JSP 2.0 is moving closer to something like
Velocity and focusing less on custom tags. Is this a correct assessment
or is there more to the 2.0 custom tags that I don't know about? (I
admit I haven't read any specs, so feel free to give me a hearty RTFM :)
I thought one of the points of JSP was to keep content/scripting looking
XML/HTML-ish for the benefit of page designers.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
