Bug 9754 - Request and response wrappers behavior
Summary: Request and response wrappers behavior
Status: RESOLVED DUPLICATE of bug 8566
Alias: None
Product: Tomcat 4
Classification: Unclassified
Component: Servlet & JSP API (show other bugs)
Version: 4.0.3 Final
Hardware: All other
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-10 18:22 UTC by Srinivas Hasti
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Srinivas Hasti 2002-06-10 18:22:03 UTC
SRV.6.2.2 Wrapping Requests and Responses says
>
> The same requirement of wrapper object identity applies to the case where
> the developer passes a wrapped request or response object into the request
> dispatcher; the request and response objects passed into the servlet
> invoked must be the same objects as were passed in.

Above statement mandates that when forward/include is done using wrappers 
we need to pass same wrapper to the servlet invoked.  The above section 
doesn't clarify whether the rule is applicable only when forward/include 
is done in the same web module or in all the cases.

Tomcat implementation doesn't pass the same wrapper with forward/include
across webmodules.

Ideally we feel that the above statement in the spec should be valid
only with in a webmodule for webmodule isolation reasons. 

If it is applicable across Webmodules then Tomcat implementation needs to be
fixed. Otherwise we would like to see the clarification in Spec.
Comment 1 Tim Funk 2003-05-30 12:07:38 UTC
dup per .. http://marc.theaimsgroup.com/?l=tomcat-dev&m=105419767921921&w=2

*** This bug has been marked as a duplicate of 8566 ***