Weird problem with JSTL

Printable View

03-01-2010, 07:57 PM
Diego_Dalmasso

Weird problem with JSTL

Hi to all,
my name's Diego and I have developed a website using JSP that connect to a MySQL server. I developed it locally using NetBeans and Tomcat. It works perfectly. I uploaded the website to a server that use also tomcat as webserver but I have problems. I used JSTL libraries. If i write in a JSP page:
<c:set var="prova" value="prova" />
<c:out value="${prova}" />
Locally: it prints "prova"
On the server: it prints "${prova}"
On the server, if instead of <c:out value="${prova}" /> I write <% out.println(prova); %> it prints "prova"
I copied the jstls jar file in WEB-INF/lib and also to tomcat/common/lib so I think that Tomcat now should support JSTL. If not, it should out an error when I try to set a variable or to print it.
I don't know what to do and I don't know what to search on google to find if someone else had the same problem. Could anyone to help me? Thank you very much
03-02-2010, 02:06 AM
FON

Here is a my previous post about setting JSTL but with Eclipse not Netbeans.

http://www.java-forums.org/new-java/24580-jstl.html

There are other solutions where you have to add <taglib> in web.xml.

Have you included standard.jar also?

Are Tomcat versions same?

How come there are no errors? Did you check catalina.out log file?
If library is not set there has to be some error?
03-02-2010, 02:51 PM
Diego_Dalmasso

Quote:

Originally Posted by FON

Here is a my previous post about setting JSTL but with Eclipse not Netbeans.

http://www.java-forums.org/new-java/24580-jstl.html

There are other solutions where you have to add <taglib> in web.xml.

Have you included standard.jar also?

Are Tomcat versions same?

How come there are no errors? Did you check catalina.out log file?
If library is not set there has to be some error?

Thank you for your replies. Finally it works but I don't know what was the problem. I tried to delete the jars, re-insert them, than I changed the URI to the previous version of JSP container and exited an error. Then I re-changed the URI to the original version and all started to work. I don't know why this happened but the important thing is that now it works :)