> >Why did the RequestDispatcher not work in the case 'A'.
> >I think it should have forwarded to /junk/first/second or to
> >/junk/second.
>
> My reading of the spec and what you've forwarded to is that the
> resulting target should be:
> /junk/second
>
> because the path you have called:
> /junk/first
>
> does not have an end slash, thus requriing the container to go back
> to the context path.
>
>
> >but it did not forward to any of these. How is the
> >RequestDispatcher supposed to work in this case??
>
> Tomcat bug I suspect. Unless Tomcat takes the call to mean forward
> to:
> /junk/firstsecond
I must tell you here that i also had a mapping for the path
/junk/firstsecond ( thinking that there may be a bug in Tomcat). but i did
not get forwarded to that also.
I had also searched the bug database for Tomcat and did not find anything
related to RequestDispatcher.
>
> But then it's inconsistent with your third case isn't it?
>
> I would say Tomcat bug is most likely answer. Probably best to raise
> it directly on their list.
>
>
> Nic
>
Gokul
___________________________________________________________________________
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
