Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 9 Jul 2003 19:18:28 -0000
Message-ID: <20030709191828.1490.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 21440]  -
    <jsp:include> whose target performs a 'forward' does not behave as
 expected

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=21440>.
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=21440

<jsp:include> whose target performs a 'forward' does not behave as expected


------- Additional Comments From pierre.delisle@sun.com  2003-07-09 19:18 -------
Agree this is severity 'minor', since this is a corner case that 
should not occur often.

> The test case 2 is giving me a headache, so I won't comment on it.

With some more coffee, I know you can do it Remy :-)

> For the first one, I think that since you're inside an include, the forwarded
> page can't close the response, which I think is very logical.

That was my impression at first, but after checking with the spec leads,
it looks like the response object is to be shared between the including and
included pages. Given the following in the servlet spec:

  - response content is sent and committed, and closed.

This would mean that the output stream of the including page is closed.

> I think the report is invalid, sorry Pierre (and even if it's not, there are
> many other, way more important request dispatcher issues which have an actual
> impact unlike this report, waiting to be clarified by the specification, 
> such as req/resp wrapping).
> I think I am against attempting to fix this bug (if confirmed it is 
> actually one) in 4.1.x.

Not sure it is invalid, but clarifications from the spec leads would
be important. I'll copy the spec leads on this report to make sure
it eventually gets addressed.

As mentioned above, this is 'minor' and I understand this may not be
fixed in 4.1.x, and that there are way more important issues pending. 
Having it logged will hopefully ensure it does not fall 
through the cracks... 
(A JSTL bug report on <c:import> is what triggered this investigation
because the behavior of <c:import> in JSTL is defined in function of <jsp:include>).

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org