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 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
Date Tue, 01 Jun 2004 19:14:33 GMT
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=29327>.
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=29327

ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null

dianne.jiao@sun.com changed:

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



------- Additional Comments From dianne.jiao@sun.com  2004-06-01 19:14 -------
To respond to Tim Funk's comment -- created a third test case attachment so that
a correct servlet path is used when place call
ServletContext.getRequestDispatcher(path_servlet).  

To respond to Remy's comment #1 - with code like this, the exception is from
Tomcat:
            try {
                rd = context.getRequestDispatcher(path_servlet);
            } catch (Exception ex) {
                out.println("Unexpected Exception thrown:" + ex.toString());
            }

To respond to Remy's comment #2 -- "it works (apparently) after setting
crossContext in DefaultContext" -- It should also return null if crossContext
not set, not just throwing an exception.   Both of them together(!!!) make the
picture complete.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message