Hi Jan,
Thanks for looking into this. The application is pretty big (one of the reasons we are porting it to v3 is to use the modularity ;)), and I screwed my gf install a few times changing back and forth with jsp-impl.jar. I will try to reproduce it in a simple example.
The runtime exception happens in this file (I added linenumbers)
1/ <%--
2/ Document : index
3/ Created on : Jul 6, 2009, 8:54:00 AM
4/ Author : joeri
5/ --%>
6/
7/ <%@taglib uri="
http://java.sun.com/jsp/jstl/core" prefix="c" %>
And the exception goes:
[#|2009-08-06T19:54:18.627+0200|WARNING|glassfish|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=29;_ThreadName=Thread-2;|StandardWrapperValve[jsp]: PWC1406: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /admin/index.jsp(7,61) PWC6188: 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
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:89)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:375)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:169)
at org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:430)
at org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:235)
at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:499)
at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:579)
at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1649)
at org.apache.jasper.compiler.Parser.parse(Parser.java:182)
at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:239)
at org.apache.jasper.compiler.ParserController.parse(ParserController.java:140)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:204)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:431)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:608)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
(followed by the usual stuff).
Hope this gives more info, and I will let you know when I have an ear reproducing the problem. Oh, this application also has custom tags, maybe that causes different behavior as well?
Thanks,
- Johan
[Message sent by forum member 'johanvos' (johanvos)]
http://forums.java.net/jive/thread.jspa?messageID=359289