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=9754>. 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=9754 Request and response wrappers behavior Summary: Request and response wrappers behavior Product: Tomcat 4 Version: 4.0.3 Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Servlet & JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
