AW: JSTL 1.1: diffs between c and c-1_0
I got it solved. After I looked up the spec I found out, that I have to use the new URIs... so changing it to http://java.sun.com/jsp/jstl/core did the trick. Dirk - I am using the jstl 1.1.1 version with the following web.xml declaration: ?xml version=1.0 encoding=UTF-8? 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 web-app_2_4.xsd version=2.4 servlet servlet-namespringapp/servlet-name servlet-classorg.springframework.web.servlet.DispatcherServlet/servlet-cl ass load-on-startup1/load-on-startup /servlet servlet-mapping servlet-namespringapp/servlet-name url-pattern*.htm/url-pattern /servlet-mapping welcome-file-list welcome-file index.jsp /welcome-file /welcome-file-list taglib taglib-urijstl/c/taglib-uri taglib-location/WEB-INF/tld/c.tld/taglib-location /taglib taglib taglib-urijstl/fmt/taglib-uri taglib-location/WEB-INF/tld/fmt.tld/taglib-location /taglib /web-app I am still facing the problem, that variables are not evaluated when using the c taglib. But it works when using c-1_0... Tomcat version is 5.0.28. Any help appreciated. Dirk -Ursprüngliche Nachricht- Von: Felipe Leme [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Oktober 2004 02:18 An: Tag Libraries Users List Betreff: Re: JSTL 1.1: diffs between c and c-1_0 On Tue, 2004-10-05 at 20:03, Dirk Manske (Mailing list) wrote: I upgraded to JSTL 1.1 because we are now using Tomcat 5. At first I tried the c.tld taglib. But this did not work. For example the result of c:out value=${aVariable} / for aVariable set to 100 was simply ${aVariable} instead of 100. Did you use the proper jars? You *must* use JSTL 1.1 on Tomcat 5, as it is a JSP 2.0 container. Note also that on JSP 2.0, the EL evaluation is done by the container (not the tag handlers) but your application must be set with the proper web.xml header (i.e., the one that uses the servlet 2.4 XML schema, and not the servlet 2.3 DTD). -- Felipe - 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]
AW: JSTL 1.1: diffs between c and c-1_0
I am using the jstl 1.1.1 version with the following web.xml declaration: ?xml version=1.0 encoding=UTF-8? 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 web-app_2_4.xsd version=2.4 servlet servlet-namespringapp/servlet-name servlet-classorg.springframework.web.servlet.DispatcherServlet/servlet-cl ass load-on-startup1/load-on-startup /servlet servlet-mapping servlet-namespringapp/servlet-name url-pattern*.htm/url-pattern /servlet-mapping welcome-file-list welcome-file index.jsp /welcome-file /welcome-file-list taglib taglib-urijstl/c/taglib-uri taglib-location/WEB-INF/tld/c.tld/taglib-location /taglib taglib taglib-urijstl/fmt/taglib-uri taglib-location/WEB-INF/tld/fmt.tld/taglib-location /taglib /web-app I am still facing the problem, that variables are not evaluated when using the c taglib. But it works when using c-1_0... Tomcat version is 5.0.28. Any help appreciated. Dirk -Ursprüngliche Nachricht- Von: Felipe Leme [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Oktober 2004 02:18 An: Tag Libraries Users List Betreff: Re: JSTL 1.1: diffs between c and c-1_0 On Tue, 2004-10-05 at 20:03, Dirk Manske (Mailing list) wrote: I upgraded to JSTL 1.1 because we are now using Tomcat 5. At first I tried the c.tld taglib. But this did not work. For example the result of c:out value=${aVariable} / for aVariable set to 100 was simply ${aVariable} instead of 100. Did you use the proper jars? You *must* use JSTL 1.1 on Tomcat 5, as it is a JSP 2.0 container. Note also that on JSP 2.0, the EL evaluation is done by the container (not the tag handlers) but your application must be set with the proper web.xml header (i.e., the one that uses the servlet 2.4 XML schema, and not the servlet 2.3 DTD). -- Felipe - 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: AW: JSTL 1.1: diffs between c and c-1_0
Dirk Manske (Mailing list) wrote: I am using the jstl 1.1.1 version with the following web.xml declaration: Remove this stuff and reload your webapp -- taglib taglib-urijstl/c/taglib-uri taglib-location/WEB-INF/tld/c.tld/taglib-location /taglib taglib taglib-urijstl/fmt/taglib-uri taglib-location/WEB-INF/tld/fmt.tld/taglib-location /taglib I am still facing the problem, that variables are not evaluated when using the c taglib. But it works when using c-1_0... Tomcat version is 5.0.28. Any help appreciated. On the same version of Tomcat, this test file works as expected: -- simple.jsp - %@ taglib uri=http://java.sun.com/jsp/jstl/core; prefix=c % c:set var=wow value=WOWSER/ h1${wow}/h1 --- If the above doesn't work for you, doublecheck you've got the right jar file in /WEB-INF/lib ... -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSTL 1.1: diffs between c and c-1_0
Dirk, Would you let me know which spec you refered to in this thread? I am trying to understand a JSTL core taglib issue that we are having. Our issue was resolved with the workaround: changing the URI attribute of our JSP [EMAIL PROTECTED] directives from /jstl-core to http://java.sun.com/jstl/core; in the pages where we used the setFormat tag. Note /jstl-core was defined in our web.xml as taglib taglib-uri/jstl-core/taglib-uri taglib-location/WEB-INF/tld/c.tld/taglib-location /taglib However, our specific issue (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15703) was supposedly fixed in JSTL 1.0.5. Release notes: http://jakarta.apache.org/taglibs/doc/standard-1.0-doc/ReleaseNotes.html. Presumably this fix would not require the above workaround. I would have thought JSTL 1.1 would not have this seemingly similar kind of issue. It seems counter intuitive to me that the URI should be a fixed value. Maybe I am missing something. I have read how-to pages which say to do this, but I have not seen any specification. Any light you can shed would be greatly appreciated. Thanks in advance for any help, Douglas Ross Developer, HTML UI Framework Kronos E-mail: [EMAIL PROTECTED] Voice: (978) 947-4305 Fax: (978) 256-2474 www.kronos.com Smaller, Faster, Sharper, Easier(tm) -Original Message- From: Dirk Manske (Mailing list) [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 6:01 AM To: 'Tag Libraries Users List' Subject: AW: JSTL 1.1: diffs between c and c-1_0 I am using the jstl 1.1.1 version with the following web.xml declaration: ?xml version=1.0 encoding=UTF-8? 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 web-app_2_4.xsd version=2.4 servlet servlet-namespringapp/servlet-name servlet-classorg.springframework.web.servlet.DispatcherServlet/servlet-cl ass load-on-startup1/load-on-startup /servlet servlet-mapping servlet-namespringapp/servlet-name url-pattern*.htm/url-pattern /servlet-mapping welcome-file-list welcome-file index.jsp /welcome-file /welcome-file-list taglib taglib-urijstl/c/taglib-uri taglib-location/WEB-INF/tld/c.tld/taglib-location /taglib taglib taglib-urijstl/fmt/taglib-uri taglib-location/WEB-INF/tld/fmt.tld/taglib-location /taglib /web-app I am still facing the problem, that variables are not evaluated when using the c taglib. But it works when using c-1_0... Tomcat version is 5.0.28. Any help appreciated. Dirk -Ursprüngliche Nachricht- Von: Felipe Leme [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Oktober 2004 02:18 An: Tag Libraries Users List Betreff: Re: JSTL 1.1: diffs between c and c-1_0 On Tue, 2004-10-05 at 20:03, Dirk Manske (Mailing list) wrote: I upgraded to JSTL 1.1 because we are now using Tomcat 5. At first I tried the c.tld taglib. But this did not work. For example the result of c:out value=${aVariable} / for aVariable set to 100 was simply ${aVariable} instead of 100. Did you use the proper jars? You *must* use JSTL 1.1 on Tomcat 5, as it is a JSP 2.0 container. Note also that on JSP 2.0, the EL evaluation is done by the container (not the tag handlers) but your application must be set with the proper web.xml header (i.e., the one that uses the servlet 2.4 XML schema, and not the servlet 2.3 DTD). -- Felipe - 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]
AW: JSTL 1.1: diffs between c and c-1_0
Hi Douglas, the jstl 1.1 spec is hosted at http://java.sun.com/products/jsp/jstl/reference/api/index.html. You can download the final or maintenance release. Dirk -Ursprüngliche Nachricht- Von: Ross, Douglas [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Oktober 2004 17:38 An: Tag Libraries Users List Betreff: RE: JSTL 1.1: diffs between c and c-1_0 Dirk, Would you let me know which spec you refered to in this thread? I am trying to understand a JSTL core taglib issue that we are having. Our issue was resolved with the workaround: changing the URI attribute of our JSP [EMAIL PROTECTED] directives from /jstl-core to http://java.sun.com/jstl/core; in the pages where we used the setFormat tag. Note /jstl-core was defined in our web.xml as taglib taglib-uri/jstl-core/taglib-uri taglib-location/WEB-INF/tld/c.tld/taglib-location /taglib However, our specific issue (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15703) was supposedly fixed in JSTL 1.0.5. Release notes: http://jakarta.apache.org/taglibs/doc/standard-1.0-doc/ReleaseNotes.html. Presumably this fix would not require the above workaround. I would have thought JSTL 1.1 would not have this seemingly similar kind of issue. It seems counter intuitive to me that the URI should be a fixed value. Maybe I am missing something. I have read how-to pages which say to do this, but I have not seen any specification. Any light you can shed would be greatly appreciated. Thanks in advance for any help, Douglas Ross Developer, HTML UI Framework Kronos E-mail: [EMAIL PROTECTED] Voice: (978) 947-4305 Fax: (978) 256-2474 www.kronos.com Smaller, Faster, Sharper, Easier(tm) -Original Message- From: Dirk Manske (Mailing list) [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 06, 2004 6:01 AM To: 'Tag Libraries Users List' Subject: AW: JSTL 1.1: diffs between c and c-1_0 I am using the jstl 1.1.1 version with the following web.xml declaration: ?xml version=1.0 encoding=UTF-8? 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 web-app_2_4.xsd version=2.4 servlet servlet-namespringapp/servlet-name servlet-classorg.springframework.web.servlet.DispatcherServlet/servlet-cl ass load-on-startup1/load-on-startup /servlet servlet-mapping servlet-namespringapp/servlet-name url-pattern*.htm/url-pattern /servlet-mapping welcome-file-list welcome-file index.jsp /welcome-file /welcome-file-list taglib taglib-urijstl/c/taglib-uri taglib-location/WEB-INF/tld/c.tld/taglib-location /taglib taglib taglib-urijstl/fmt/taglib-uri taglib-location/WEB-INF/tld/fmt.tld/taglib-location /taglib /web-app I am still facing the problem, that variables are not evaluated when using the c taglib. But it works when using c-1_0... Tomcat version is 5.0.28. Any help appreciated. Dirk -Ursprüngliche Nachricht- Von: Felipe Leme [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Oktober 2004 02:18 An: Tag Libraries Users List Betreff: Re: JSTL 1.1: diffs between c and c-1_0 On Tue, 2004-10-05 at 20:03, Dirk Manske (Mailing list) wrote: I upgraded to JSTL 1.1 because we are now using Tomcat 5. At first I tried the c.tld taglib. But this did not work. For example the result of c:out value=${aVariable} / for aVariable set to 100 was simply ${aVariable} instead of 100. Did you use the proper jars? You *must* use JSTL 1.1 on Tomcat 5, as it is a JSP 2.0 container. Note also that on JSP 2.0, the EL evaluation is done by the container (not the tag handlers) but your application must be set with the proper web.xml header (i.e., the one that uses the servlet 2.4 XML schema, and not the servlet 2.3 DTD). -- Felipe - 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]
JSTL 1.1: diffs between c and c-1_0
Hi, I upgraded to JSTL 1.1 because we are now using Tomcat 5. At first I tried the c.tld taglib. But this did not work. For example the result of c:out value=${aVariable} / for aVariable set to 100 was simply ${aVariable} instead of 100. When I changed the c taglib to c-1_0.tld I got the expected result 100. But this seems to me as when I am using the old c taglib version 1.0. So for what is c.tld from the JSTL 1.1 package good for?! I could not find anything in the spec about the diffs between c and c-1_0, maybe there is someone out there who can give me advise. thanks, dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSTL 1.1: diffs between c and c-1_0
On Tue, 2004-10-05 at 20:03, Dirk Manske (Mailing list) wrote: I upgraded to JSTL 1.1 because we are now using Tomcat 5. At first I tried the c.tld taglib. But this did not work. For example the result of c:out value=${aVariable} / for aVariable set to 100 was simply ${aVariable} instead of 100. Did you use the proper jars? You *must* use JSTL 1.1 on Tomcat 5, as it is a JSP 2.0 container. Note also that on JSP 2.0, the EL evaluation is done by the container (not the tag handlers) but your application must be set with the proper web.xml header (i.e., the one that uses the servlet 2.4 XML schema, and not the servlet 2.3 DTD). -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]