JasperException: absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved [duplicate]
I've been having the following problem with my GoDaddy's server. I am using JSPs with the JSTL Library. My /WEB-INF/lib folder contains the following libraries:
jstl.jar standard.jar
My JSP looks something like this:
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<p>Hello! <%
out.print(System.getProperty("java.class.path"));
%></p>
But I keep getting the following exception:
org.apache.jasper.JasperException: The absolute uri:
http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml
or the jar files deployed with this application
Any ideas as to why it is doing that?
You need to get the right version of JSTL, they use different URIs.
If that one's not working, try: http://download.java.net/maven/1/jstl/jars/jstl-1.2.jar (JSTL 1.2), or pull down the 1.1 JSTL jars.
There's a more detailed list of versions/URIs at coderanch.
you need to add Following jar file in your web application
jakarta-jstl-1.1.2.jar
and jakarta-standard-1.1.2.jar files
Recently I have same problem, that i have resolved by adding above two jar files
I used Tomcat6 37. As for me, I tried mentioned above solutions but still got the error. The problem solved after adding the jstl-1.2.jar to my %CATALINA_HOME%\lib directory.
The answers here were useful to explain the problem but it did not help me diagnose why it was happening when I thought I was loading the right JSTL versions. Ultimately I had to debug the application and put a breakpoint in the TLD file processor (maybe org.apache.jasper.compiler.TagLibraryInfoImpl.getTagLibraryInfos()
) to see from where it was getting the TLD files.
I then discovered that it was loading old versions of the TLD files from a jar that I did not suspect had them -- it was a dependency of the GWT (ick) subsystem. Once the offending jar was removed from my maven dependencies, the problem was resolved.
Hopefully this will help someone else in the future.
精彩评论