Shouldn't you first reference the standard tag libraries in your jsp page, such
as:
%@ taglib prefix=c uri=http://java.sun.com/jstl/core%
and then use the core 'out' function, such as:
Welcome, c:out value=${user.firstName} /!
And you will need jstl.jar and standard.jar in WEB-INF/lib.
View
Not really. EL is part of JSP 2.0 and has nothing to do with JSTL. Also,
displaying things immediately using EL without needing a c:out tag is quite
handy. So, any ideas on this? Is EL somehow turned off by JBoss?
View the original post :
I put in this page directive in my JSP:
%@ page isELEnabled=true%
and when I accessed the page I got:
org.apache.jasper.JasperException: /index.jsp(1,1) Page directive has invalid
attribute: isELEnabled
which indicates to me that JBoss is somehow not providing me with JSP 2.0. Is
this
Well I think I found the problem. The class javax.el doesn't appear in any of
the jars that ship with JBoss 4.0.4. So it looks like JBoss is in fact
shipping with an older JSP setup.
So I need to somehow install the new JSP jars and have JBoss use those instead.
Any suggestions on this?
Never mind about that last post, that isn't right. javax.el.* is of course
part of J2EE. JBoss should ship with an implementation of that package.
That's where the problem is. Tomcat does have an implementation, but JBoss
does not appear to, which I don't understand.
View the original
Are you sure that it is in Tomcat? I just checked 5.5.17 and none of the jars
contain the javax.el.* package. (Just wondering if you enhanced Tomcat or
installed as part of some other package, and that is how you got javax.el.*. I
know that kind of a situation has happened to me before.)
The problem is solved. As usual, it is something absolutely trivial, which
does not show up on any debugging tool. The web.xml doctype was for 2.2, not
2.4. What a difference 0.2 makes. Because the doctype was for an older app,
it was giving me JSP 1.2 or whatever, when I need JSP 2.0.
