JSP 2.0 in Tomcat 5.0.4
It's my understanding that JSTL is an integral part of any JSP 2.0-compliant container. To me, this means that I shouldn't have to include jstl.jar/standard.jar in my app's WEB-INF/lib folder. I would also assume that I don't need to declare the JSTL tags as a directive: %@ taglib uri=http://java.sun.com/jstl/core; prefix=c % %@ taglib uri=http://java.sun.com/jstl/fmt; prefix=fmt % However, this doesn't seem to be the case with JSP 2.0 in the jsp-examples that ship with Tomcat 5.0.4: 1. WEB-INF/lib contains jstl.jar and standard.jar 2. If I don't have a taglib declaration, c:if is not interpreted in a JSP in this project. Please fill me on on what I need to do for a JSP 2.0-compliant app. Do I need to include jstl.jar and standard.jar in WEB-INF/lib? Do I need to declare the taglibs when using fmt and c:...? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP 2.0 in Tomcat 5.0.4
EL is integral to the jsp2 spec. Not jstl. EL is based off of jstl.
From a quick glance at the spec, I see in Section 4:
References to JSTL are informational - this library is not required by the
JSP 2.0 specification.
If you search for JSTL in the spec, its seems clear that if you want JSTL:
you still need the classes and taglib declarations. The difference with JSP2
is you can now do this syntax without needing JSTL:
Hello ${someVariable} (woohoo, no c:out needed!)
I think you can also do this now too .. mytag myattr=${elExpression}/
But to do a loop (c:foreach) - you still need JSTL. You'll even see the
taglib declarations for the JSTL core taglib in the examples in the spec.
-Tim
Raible, Matt wrote:
It's my understanding that JSTL is an integral part of any JSP 2.0-compliant
container. To me, this means that I shouldn't have to include
jstl.jar/standard.jar in my app's WEB-INF/lib folder. I would also assume
that I don't need to declare the JSTL tags as a directive:
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c %
%@ taglib uri=http://java.sun.com/jstl/fmt; prefix=fmt %
However, this doesn't seem to be the case with JSP 2.0 in the jsp-examples
that ship with Tomcat 5.0.4:
1. WEB-INF/lib contains jstl.jar and standard.jar
2. If I don't have a taglib declaration, c:if is not interpreted in a JSP
in this project.
Please fill me on on what I need to do for a JSP 2.0-compliant app. Do I
need to include jstl.jar and standard.jar in WEB-INF/lib? Do I need to
declare the taglibs when using fmt and c:...?
Thanks,
Matt
-
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]
RE: JSP 2.0 in Tomcat 5.0.4
Understood - thanks for the clear, and to the point error.
Doesn't that mean that the following should work?
c:set var=bodyId scope=request
tiles:getAsString name=body.id ignore=true/
/c:set
body id=${requestScope.bodyId}?
Or just body id=${bodyId}
Because it doesn't work for me. Do I have to use the 2.4 in web.xml to make
this work?
Thanks,
Matt
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 7:27 AM
To: Tomcat Users List
Subject: Re: JSP 2.0 in Tomcat 5.0.4
EL is integral to the jsp2 spec. Not jstl. EL is based off of jstl.
From a quick glance at the spec, I see in Section 4:
References to JSTL are informational - this library is not required by the
JSP 2.0 specification.
If you search for JSTL in the spec, its seems clear that if you want JSTL:
you still need the classes and taglib declarations. The difference with JSP2
is you can now do this syntax without needing JSTL:
Hello ${someVariable} (woohoo, no c:out needed!)
I think you can also do this now too .. mytag myattr=${elExpression}/
But to do a loop (c:foreach) - you still need JSTL. You'll even see the
taglib declarations for the JSTL core taglib in the examples in the spec.
-Tim
Raible, Matt wrote:
It's my understanding that JSTL is an integral part of any JSP
2.0-compliant
container. To me, this means that I shouldn't have to include
jstl.jar/standard.jar in my app's WEB-INF/lib folder. I would also assume
that I don't need to declare the JSTL tags as a directive:
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c %
%@ taglib uri=http://java.sun.com/jstl/fmt; prefix=fmt %
However, this doesn't seem to be the case with JSP 2.0 in the jsp-examples
that ship with Tomcat 5.0.4:
1. WEB-INF/lib contains jstl.jar and standard.jar
2. If I don't have a taglib declaration, c:if is not interpreted in a
JSP
in this project.
Please fill me on on what I need to do for a JSP 2.0-compliant app. Do I
need to include jstl.jar and standard.jar in WEB-INF/lib? Do I need to
declare the taglibs when using fmt and c:...?
Thanks,
Matt
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSP 2.0 in Tomcat 5.0.4
I meant clear and to the point *answer* not error. ;-)
-Original Message-
From: Raible, Matt
Sent: Thursday, July 17, 2003 7:52 AM
To: 'Tomcat Users List'
Subject: RE: JSP 2.0 in Tomcat 5.0.4
Understood - thanks for the clear, and to the point error.
Doesn't that mean that the following should work?
c:set var=bodyId scope=request
tiles:getAsString name=body.id ignore=true/
/c:set
body id=${requestScope.bodyId}?
Or just body id=${bodyId}
Because it doesn't work for me. Do I have to use the 2.4 in web.xml to make
this work?
Thanks,
Matt
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 7:27 AM
To: Tomcat Users List
Subject: Re: JSP 2.0 in Tomcat 5.0.4
EL is integral to the jsp2 spec. Not jstl. EL is based off of jstl.
From a quick glance at the spec, I see in Section 4:
References to JSTL are informational - this library is not required by the
JSP 2.0 specification.
If you search for JSTL in the spec, its seems clear that if you want JSTL:
you still need the classes and taglib declarations. The difference with JSP2
is you can now do this syntax without needing JSTL:
Hello ${someVariable} (woohoo, no c:out needed!)
I think you can also do this now too .. mytag myattr=${elExpression}/
But to do a loop (c:foreach) - you still need JSTL. You'll even see the
taglib declarations for the JSTL core taglib in the examples in the spec.
-Tim
Raible, Matt wrote:
It's my understanding that JSTL is an integral part of any JSP
2.0-compliant
container. To me, this means that I shouldn't have to include
jstl.jar/standard.jar in my app's WEB-INF/lib folder. I would also assume
that I don't need to declare the JSTL tags as a directive:
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c %
%@ taglib uri=http://java.sun.com/jstl/fmt; prefix=fmt %
However, this doesn't seem to be the case with JSP 2.0 in the jsp-examples
that ship with Tomcat 5.0.4:
1. WEB-INF/lib contains jstl.jar and standard.jar
2. If I don't have a taglib declaration, c:if is not interpreted in a
JSP
in this project.
Please fill me on on what I need to do for a JSP 2.0-compliant app. Do I
need to include jstl.jar and standard.jar in WEB-INF/lib? Do I need to
declare the taglibs when using fmt and c:...?
Thanks,
Matt
-
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]
-
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]
Re: JSP 2.0 in Tomcat 5.0.4
To use EL - you need a web.xml that says it is a 2.4 webapp. I think by
default - EL is enabled and it can be turned off by url.
But you'll need to see the spec for the intricacies of using EL in your own
tag. (So you know the rules of setting data, primitives vs objects vs
casting. I haven't the foggiest idea of what they are. I could guess, but I'd
be wrong and end up reading the spec. )
-Tim
Raible, Matt wrote:
Understood - thanks for the clear, and to the point error.
Doesn't that mean that the following should work?
c:set var=bodyId scope=request
tiles:getAsString name=body.id ignore=true/
/c:set
body id=${requestScope.bodyId}?
Or just body id=${bodyId}
Because it doesn't work for me. Do I have to use the 2.4 in web.xml to make
this work?
Thanks,
Matt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
