tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3665] - Request Dispatching - Parameters are not properly set
Date Tue, 18 Sep 2001 00:11:19 GMT
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=3665>.
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=3665

craig.mcclanahan@sun.com changed:

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



------- Additional Comments From craig.mcclanahan@sun.com  2001-09-17 17:11 -------
The problem is that setting a request attribute to a null value is not legal
(same for session attributes and servlet context attributes).  Therefore, not
setting the "javax.servlet.include.path_info" attribute is the appropriate
indication to the included servlet that it was invoked with no extra path info.

Same thing happens on the query string attribute if there is no query string on
the path passed to getRequestDispatcher().

Note that Tomcat's current behavior is what the J2EE compatibility tests are
looking for, so you will find it to be portable across all containers.

Mime
View raw message