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


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From [EMAIL PROTECTED]  2006-09-29 19:41 -------
(In reply to comment #8)
> The quote from the spec is:
> <quote>
> The parameters to these methods can be either...
> </quote>
> Can is not the same as must. The language as currently written does not mean
> that the only permitted parameters are the original request/response or the
> wrapped request/response. The example given in comment 5 is perfectly valid 
for
> the current spec language.

You are so wrong here:
<spec-quote version="2.4" section="14.2.5.1">
The request and response parameters must be either the same objects as were
passed to the calling servlet’s service method or be subclasses of the
ServletRequestWrapper or ServletResponseWrapper classes that wrap
them.
</spec-quote>

That means you can use the Request/Response that Tomcat passes in, or a 
HttpServletRequest/ResponseWrapper that wraps the Request/Response that Tomcat 
passes in. And that is it.  The example in #5 isn't valid wrt the spec.


-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to