Oussama M Billah wrote:1) change the URI from
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
to <%@ taglib uri="http://java.sun.com/jstl/core_rt" prefix="c" %>
Bear Bibeault wrote:
Oussama M Billah wrote:1) change the URI from
&lt;%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %&gt;
to &lt;%@ taglib uri="http://java.sun.com/jstl/core_rt" prefix="c" %&gt;
That just switched you back to JSTL 1.0. No good.
Is your deployment descriptor properly declared using Servlets 2.4 Schema (as described in the JSP FAQ)?
Bear Bibeault wrote:Using code tags this time, please post the tag that is causing the issue. The code in your original post is not readable.
Please read this for more information.
Bear Bibeault wrote:What are the <s:> tags? My guess is those are the issue. Are they JSP 2.0 compatible?
David Newton wrote:It's not that they're "incompatible" with JSP 2.0, it's that we don't allow JSP EL expressions in their attributes to avoid a security issue.
Some people just extract the TLD, remove the restriction, and either use that TLD or re-jar it back up. Or, in your case, just use <s:iterator> and skip the JSTL tags, or make sure <c:foreach> puts the iterated value into one of the normal JEE scopes and use an OGNL expression, which will check the scopes as well.
Reference the correct JSTL uri in your JSP,change
CLUCK LIKE A CHICKEN! Now look at this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|