>>> "Craig R. McClanahan" <[EMAIL PROTECTED]> 31-Aug-00
8:35:09 PM >>>
> It does seem to be a bug.... Craig?
>Could the original poster please re-post the problem description,
>along with the relevant parts of the web.xml file? In addition, it
>is important to understand what context path this app is running
>under.
Extracts from Gokul's original mail:
>Context path here was /junk
>available servlet mappings in my web.xml are
>/first
>/first/
>/first/abc
>/second
>/first/second
>/first/abc/second
>Cases tried out.
>A)
> 1) called /junk/first
> 2) Got RequestDispathcher by the method =
>response.getRequestDispatcher("second");
> -- Got a RequestDispathcer which was not null but could not
forward
> to it. The message got was page not found.
> B)
> 1) called /junk/first/
> 2) Got RequestDispathcher by the method
> response.getRequestDispatcher("second");
> -- Got forwarded successfully to /junk/first/second
> C)
> 1) called /junk/first/abc
> 2) Got RequestDispathcher by the method
> response.getRequestDispatcher("second")
> -- Got forwarded successfully to /junk/first/second
It's the ambiguity introduced by the difference between results from
cases A and C that is at issue.
It seems to me that A should return an RD pointing to the mapping:
/junk/second
Gokul told me later he had also added a mapping for:
/firstsecond
in case Tomcat was simply appending the path for the relative call to
the servletPath. He tells me this didn't work either (ie: the RD that
was got did not point to "/junk/firstsecond").
Nic
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
