You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2005/11/01 16:27:07 UTC
DO NOT REPLY [Bug 37320] New: -
Failing to resolve a (previously resolved) tag during page compilation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37320>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37320
Summary: Failing to resolve a (previously resolved) tag during
page compilation
Product: Tomcat 5
Version: 5.5.12
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: normal
Priority: P3
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: andrew@acooke.org
I have a JSP page that compiles fine when the contents have the form:
<%@ include file="/WEB-INF/jsp/include/headers.jsp" %>
<%@ page import="..." %>
<input type="hidden" name="show" value="contacts"/>
<collab:block>
<collab:titlemain key="member-contacts"/>
<collab:body>
<spring:nestedPath path="command.contacts">
<%--
<spring:nestedPath path="names">
</spring:nestedPath>
--%>
...
However, when the second nestedPath is present (comments above removed) I see
the error:
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
_jspx_nestedPath_1 cannot be resolved
Generated servlet error:
_jspx_nestedPath_1 cannot be resolved
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:409)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:288)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:604)
at org.apache.struts.tiles.TilesUtilImpl.doInclude(TilesUtilImpl.java:99)
at org.apache.struts.tiles.TilesUtil.doInclude(TilesUtil.java:135)
...
I realise that this is a very common error, generally caused by
mis-configuration. But in this case the failure is triggered by a repeated
reference to a tag that was resolved just a line earlier. So it is difficult to
see how incorrect configuration can be the explanation.
Currently I do not have a simple version of this problem - it is part of a
project that is under development. I can ftp the entire Eclipse project
somewhere if that is of any help.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org