- This topic has 3 replies, 3 voices, and was last updated 18 years, 9 months ago by
.
-
Posts
-
Just a ‘heads up’ for any one else that might run into this problem.
If you see EL expressions come through unprocessed in your JSPs and you are using JSTL 1.1 on Tomcat 5.5.x, check your web.xml for Servlet 2.3 markup.
If you have:
<!DOCTYPE web-app PUBLIC “-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN” “http://java.sun.com/dtd/web-app_2_3.dtd”>
<web-app>instead of
<web-app xmlns=”http://java.sun.com/xml/ns/j2ee” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” version=”2.4″ xsi:schemaLocation=”http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd”>
the problem is right there in your web.xml.
This is only relevant to MyEclipse in that if you don’t start out your project choosing JSTL 1.1 then MyEclipse will give you the 2.3 version of web.xml.
The version of the web.xml is determined when you create a a new Web Project or add Web Capabilities. You are asked for the level of J2EE compatability that you wish to use (1.3 or 1.4). The previous uses the web 2.3 spec and the later uses the web 2.4 spec.
This has nothing to do with the version of JSTL you add, the choice of the web.xml file is made before this.
The 2.3/2.4 issue had me stymied for a bit. I was experimenting with xdoclet and had gone through the myeclipse xdoclet tutorials (http://myeclipseide.com/Articles/XDocletWebTutorial.html) there is a section that explicitly sets the depolyment descriptor version number to 2.3 and after going through the rest I ran and redeployed and EL started not being processed.
Perhaps adding a note in that tutorial is called for?
