Hi,
last night i stepped during the upgrade from TC4 to TC5 and from
JSTL1.0 to JSTL1.1 into the same problem. And fortunately changing the
2.3er DTD entry to an 2.4er Schema entry solved my problem.
But i dont know why.
What has this entry to do with the execution of JSTL-Expressions?
On Tue, 14 Dec 2004 12:09:12 -, Allistair Crossley
[EMAIL PROTECTED] wrote:
it instructs tomcat to use the expression language engine I *think*
hmm..., but before (TC 4.0.6 - JSTL1.0 - DTD 2.3) all works fine.
Upgrading only the Tomcat, the JSTL-Jars, the JSTL-URIs in the JSPs
without
it instructs tomcat to use the expression language engine I *think*
-Original Message-
From: Thomas Chille [mailto:[EMAIL PROTECTED]
Sent: 14 December 2004 12:07
To: Tomcat Users List
Subject: Re: JSP expressions are displayed as string
Hi,
last night i stepped during
web.xml
- web.xml says el is disabled for that page
- the jsp has el ignored
- you haven't included the fn tag lib (doubt this)
-Tim
haimra wrote:
I am having this wired problem driving me crazy.
I am using JSTL and Tomcat 5.0.30.
Some times for unknown reason the JSP expressions are displayed
for unknown reason the JSP expressions are displayed as string
for example
The following command
c:out value=${fn:escapeXml(param.code)}/
will display the expressions fn:escapeXml(param.code)
and not the actual value of param.code
Any clue why this happens
I replaced my web-app tag with the following tag in my web.xml
web-app xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
version=2.4
Then I
I am having this wired problem driving me crazy.
I am using JSTL and Tomcat 5.0.30.
Some times for unknown reason the JSP expressions are displayed as string
for example
The following command
c:out value=${fn:escapeXml(param.code)}/
will display the expressions fn:escapeXml
