If I understand correctly, a JSP 2.0 container will let you use EL 2.0 expressions
anywhere in the jsp body without having to use the JSTL tags. I also believe that
Tomcat 5 is a JSP 2.0 container, and that support may already be there, I have no idea
though. Someone else may be able to
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
Message -
From: Shawn Bayern [EMAIL PROTECTED]
To: Tag Libraries Users List [EMAIL PROTECTED]
Sent: Friday, March 21, 2003 9:08 AM
Subject: Re: Evaluating BodyContent
JSP 2.0 (for which standard Tomcat 5.0 is a compliant container) shifts
the responsibility of evaluating EL expressions
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
On 21 Mar 2003, Dave Newton wrote:
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
The only change is that expressions will be promoted to the level of
scripting expressions in order to simplify page syntax; the focus hasn't
changed. In other words, instead of
%= pageContext.findAttribute(foo) %
you'd simply write
${foo}
Right, but I thought the approved way to
If I had a tag that created HTML markup would that still be the
canonical way to create that markup? In other words is EL the
designated way to grab values from various scopes but not for simple
variable lookup?
I'm not sure I understand the question, but one of JSP 2.0's advantages is
On 21 Mar 2003, Dave Newton wrote:
I guess my curiosity just comes from the apparent abandonment of the
c:out.../ tag in favor of the obviously simpler EL expressions that
look like previously-existing solutions is all.
I'm not complaining; it's better from the brevity-standpoint, it's
On Fri, 2003-03-21 at 16:52, Shawn Bayern wrote:
I see what you're saying, but XML-looking is vague and not particularly
a target. The advantage of ${foo} to %= foo % is that it can be used in
the middle of otherwise well-formed XML documents; JSP continues to
provide an XML syntax. In fact,
On 21 Mar 2003, Dave Newton wrote:
Hmm, that's true about the well-formed comment. If one of the goals
(WAS one of the goals?) was to remove scriptlets, though, isn't the
${foo} just some syntactic sugar around a %=..%?
Honestly, I wasn't trying to start anything :D
No, these are all good
- As I said before, the syntax is compatible with well-formed XML,
and it's shorter and more convenient for page authors.
No, really, I enjoy typing all the extra. Honest. Really.
Tragically, my emacs wonder-macro that expanded ${thang} to the
equivalent c:out.../ will be rendered useless
11 matches
Mail list logo
