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=32014>. 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=32014 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2005-02-21 23:04 ------- Thanks for doing the digging, Mike. Remy's (typically terse) response on your Tomcat bug report is accurate, but he didn't point you at why that's the case. In particular, see SRV.8.2, first para: To use a request dispatcher, a servlet calls either the include or forward method of the RequestDispatcher interface. The parameters to those methods can be either the request and response arguments that were passed in via the service method of the javax.servlet interface, or instances of subclasses of the request and response wrapper classes that were introduced for version 2.3 of the specification. In the latter case, the wrapper instances must wrap the request or response objects that the container passed into the service method. In essence, this means that the wrapper inserted by the dispatcher logic goes UNDERNEATH your application wrapper, rather than on top of it. Before RD: MyWrapper --> ContainerRequest After RD: MyWrapper -> RequestDispatcherWrapper --> ContainerRequest The intent of this was that an application that wrapped a request, then dispatched to another servlet, could assume that the "top" request was still its own, and could therefore be cast directly to the custom wrapper class. In retrospect, that might not have been the best choice (the receiving servlet could easily walk down the chain of wrappers until it found its own), but we're stuck with it. Unfortunately, that means (as I think I've seen stated on a couple of the other bug reports in this area) that a wrapper as currently included in Struts-Faces cannot be used to solve the problem it is intended to solve -- we'll need to find another way. I'm going to rip it out of the code. The only good news (if you can call it that :-) is that I can close this bug. -- 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]
