Well,
<JSTL l.0 spec>
Supporting the EL in a JSP 1.2 environment
There were quite a few issues involved with the support of an expression
language
within JSTL given the constraint that it had to work with JSP 1.2
containers. In order
to be able to support both the scripting (rtexprvalues) and the EL
(elexprvalues)
worlds, we came up with the concept of twin tag libraries: one that
supports the
expression language, and one that supports request time expression
values. The
assumption is that people will mostly use the EL-based tag libraries,
while it is still
possible for page authors that prefer scripting to use JSTL with
rtexprvalues
(provides benefits for type safety and performance) via the RT-based tag
libraries.
The URIs of the RT-based tag libraries simply have the "_rt" suffix
appended. It is
allowed to mix both EL- and RT- based actions as shown in the following
example:
<fmt:message key="attendanceAgeAverage">
<fmt:param value="${totalParticipants}">
<fmt_rt:param value="<%=Stats.ageAverage(participants)%>"/>
</fmt:message>
</JSTL l.0 spec>
As you see runtime expressions were quite valid in jstl 1.0 tags.
I couldn't find information in jstl 1.1 / jsp 2.0 regarding this issue.
That is why I would appreciated the pointers to the specs.
--Seva
-----Original Message-----
From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 4:23 PM
To: Tomcat Users List
Subject: Re: org.apache.jasper.JasperException using jsp expression
inside the <c:set />
On 8/24/05, Seva Popov <[EMAIL PROTECTED]> wrote:
> Hi Rahul,
>
> Thanks for pointing me to the implicit JSP 2.0 param object. This
worked
> for me perfectly with the JSP 2.0 JSTL URIs:
>
> <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page";
> xmlns:c="http://java.sun.com/jsp/jstl/core";
> version="2.0">
> <c:set var="admin" value="${param.admin}" />
>
>
> Anyway, I'd be interested to hear from somebody (with the pointers to
> the JSP or JSTL specs if possible) why
>
> <c:set var="admin" value="<%=request.getParameter("admin")%>"/>
>
> worked for me with the latest Resin and doesn't with the latest
Tomcat.
>
> Is it against the specs?
<snip/>
You mean, apart from the fact that it is invalid XML and hence cannot
be part of a jspx document (such as the one you are using)? ;-)
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
