url matching doubt

[Harshana Dias]

Hey,

1. In directory match was is necessary to have the end slash also.

eg:

<servlet>
<servlet-name>one</servlet-name>
<servlet-class>foo.Abc</servlet-class>
</servlet>

<servlet-mapping>
<url-pattern>/abc/*</url-patter>  // i am talking about this slash before *
<servlet-name>one</servlet-name>
</servlet-mapping>

is this servlet match with the following request as directory match?
http://localhost/Test/abc (no end slash like /abc/)


2.It was said that if a request match more than one url-pattern container will choose the longest mapping also it was said container will first look for exact match , directory match and then extension map. so its kind of contradictory know? since the exactly match is the longest this wouldnt be a problem? but what if we choose both exact and directory match have the same length.
eg:

<url-pattern>/foo/bar/vvv<url-pattern>
<url-pattern>/foo/bar/vvv/*<url-pattern>

[Sebastian Janisch]

In this case the exact match will always win.

As for the slash, a mapping of /dir/* and a request of http://localhost:8080/PROJECT_NAME/dir will also map to the corresponding servlet.

[Harshana Dias]

Ive found this article also it says if that slash not there it will need a exact macth..

That would be an unmatched pattern since the * would not be a wildcard, but must be an exact match

reference:
http://www.coderanch.com/t/422371/Servlets/java/HttpServletRequest-getRequestDispatcher-behaving-strangely