You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/02/02 08:25:58 UTC
[Bug 87] New - Request Dispatcher violates Servlet Spec BugRat Report#57
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=87
*** shadow/87 Thu Feb 1 23:25:58 2001
--- shadow/87.tmp.13262 Thu Feb 1 23:25:58 2001
***************
*** 0 ****
--- 1,42 ----
+ +============================================================================+
+ | Request Dispatcher violates Servlet Spec BugRat Report#57 |
+ +----------------------------------------------------------------------------+
+ | Bug #: 87 Product: Tomcat 3 |
+ | Status: RESOLVED Version: Nightly Build |
+ | Resolution: INVALID Platform: All |
+ | Severity: Normal OS/Version: All |
+ | Priority: High Component: Servlet |
+ +----------------------------------------------------------------------------+
+ | Assigned To: bugzilla@apache.org |
+ | Reported By: anonymous-bug@cortexity.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ These are the first two lines of the forward and include methods:
+
+ Request realRequest = ((HttpServletRequestFacade)request).getRealRequest();
+ Response realResponse = ((HttpServletResponseFacade)response).getRealResponse();
+
+ You are explicitly casting to some Tomcat specific request class. How are we suppposed
+ to be able to write our own response class and still be able to move between different
+ application servers. You are totally screwing up the whole idea of having a servlet spec.
+
+ For example say I wanted to output my jsp to a file instead of the browser. I could write
+ my own dummy response that overides the getOutputStream method. I can't do this though because
+ my dummy Response is not a HttpServletRequestFacade class.
+
+ I know that there are other ways to do this. This is just one simple example but there are many
+ other things we could do if you didn't box us into a corner by requiring the request and response to
+ be your "Facade" classes.
+
+ James
+ james@intellimedia.com
+
+ ------- Additional Comments From cmanolache@yahoo.com 2001-02-01 23:25 -------
+ I totally agree, but:
+ "The request and response parameters must be the same
+ objects as were passed to the calling servlet's service method"
+ You can use servlet2.3 filters.
+ Sorry about that - I don't like it either.