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 2002/09/12 17:03:08 UTC
DO NOT REPLY [Bug 12578] New: -
JSP forward not working OK from JSP include
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12578>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12578
JSP forward not working OK from JSP include
Summary: JSP forward not working OK from JSP include
Product: Tomcat 4
Version: 4.0.4 Final
Platform: All
OS/Version: Other
Status: NEW
Severity: Major
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: yair.lenga@ssmb.com
My main JSP file include other JSP files, some of them are simply "forward" to
the real context page (also a JSP file). It looks that if page "a" does
"jsp:include" to page "b", which will use "jsp:forward" to different page "c",
then the output of "c" will replace the output of "a".
It looks as if a "forwarded" in an included page will cause the "main" page to
be replaced by the "forMy structure looks like:
Main file "a.jsp"
<h1> BEGIN </h1>
<jsp:include page="a1.jsp" />
<jsp:include page="a2.jsp" />
<jsp:include page="a3.jsp" />
</h1> END </h1>
The small files a1.jsp, a2.jsp, a3.jsp contain:
a1.jsp: <jsp:forward page="a1x.jsp" />
a2.jsp: <jsp:forward page="a2x.jsp" />
a3.jsp: <jsp:forward page="a3x.jsp" />
The files a1x.jsp, a2x.jsp, a3x.jsp contain:
a1x.jsp: <h1> a1x </h1>
a2x.jsp: <h1> a2x </h1>
a3x.jsp: <h1> a3x </h1>
The pages are placed into the ROOT context of a default TOMCAT install. When the
page is fetched I was expecting:
BEGIN
a1x
a2x
a3x
END
Instead, I'm only seeing:
a1x
It looks as if the <page:forward> in "a1.jsp", cause the whole request to be
forwarded to "a1x.jsp". Instead of just forwarding the "a1.jsp" request to
"a1x.jsp", it behave as if the forward request was issues from "a.jsp".
I checked the code with Jrun - and it behaves the way I expect it to be. I'm not
if the specification are clean about this behavior, but this behavior is wrong.
It will cause a JSP page to behave differently if any included page is using the
"jsp:forward" directive.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>