Matching URL pattern with @RequestMapping

Question

It's quite similar to this question, but I just couldn't figure out how to match the url pattern.

web.xml:

<servlet-mapping>
        <servlet-name>dispatcher</servlet-name>
        <url-pattern>/activate/*</url-pattern>
</servlet-mapping>

My controller:

@RequestMapping(value = {"activate/{key}"}, method = RequestMethod.GET)
public ModelAndView activate(@PathVariable(value = "key") String key) {
  ...
}

When I try to access localhost:9999/myApp/activate/123456789, I get the following error:

No mapping found for HTTP request with URI [/myApp/activate/123456789] in DispatcherServlet with name 'dispatcher'

I also tried <url-pattern>/*</url-pattern>, same thing happens.

However, by changing <url-pattern>/activate/*</url-pattern> to <url-pattern>/**</url-pattern> no error appears, but i still get 404. So, how do I map this url pattern?

Try adding a '/' at the beginning of your request mapping and see if that makes a difference. It should work with url-pattern /* and access it with /contextPath/activate/123456789. Also, check your logs for any startup errors that might have caused the web application to not have started properly. — NilsH
– NilsH, Commented Mar 28, 2013 at 14:12

Deividi Cavarzan · Accepted Answer · 2013-03-28 14:32:06Z

3

You need to put slash on @RequestMapping, like:

@RequestMapping(value = {"/activate/{key}"}, method = RequestMethod.GET)
public ModelAndView activate(@PathVariable(value = "key") String key) {
  ...
}

Anyway, if you wat to get access to following context:

<servlet-mapping>
        <servlet-name>dispatcher</servlet-name>
        <url-pattern>/activate/</url-pattern>
</servlet-mapping>

You cant try this:

@RequestMapping(value = {"/{key}"}, method = RequestMethod.GET)
public ModelAndView activate(@PathVariable(value = "key") String key) {
  ...
}

[Edited]

Like Leonel said, you should have this configuration to use with full URL (@RequestMapping(value = {"/activate/{key}"}):

<url-pattern>/</url-pattern>

edited Mar 28, 2013 at 14:32

answered Mar 28, 2013 at 14:16

Deividi Cavarzan

10.1k13 gold badges68 silver badges80 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Alpha Carinae Over a year ago

OK, it works. But it causes redirect loop in my case. For example, if the activation is successful, I redirect it by new ModelAndView(redirect:./success) and it gets root directory as myApp/activate, so 'success' matches /{key}. But I want my root to be myApp only. Should I use full path to solve this or is there any other way?

Deividi Cavarzan Over a year ago

Hum, I think that you need to use full path URL with <url-pattern>/</url-pattern> to user 'myApp' as root.

Leonel · Accepted Answer · 2013-03-28 14:30:46Z

2

Change the url-pattern element to the following. A single slash, no asterisk:

<url-pattern>/</url-pattern>

What happens is, first the servlet container matches the requested URL into the pattern, and then it calls Spring's DispatcherServlet, which dispatches to the correct controller.

When you have the slash + asterisk, /*, the snippet of the URI /activate/123456789 is matched, which leaves the empty string for the DispatcherServlet to find the controller.

When you have the single slash, /, only the slash is matched by the servlet container, which leaves the string /activate/123456789 to be matched by the DispatcherServlet; with this string, the DispatcherServlet is able to find the controller.

answered Mar 28, 2013 at 14:30

Leonel

29.4k26 gold badges82 silver badges107 bronze badges

2 Comments

Sotirios Delimanolis Over a year ago

You don't just lose URL substrings because the DispatcherServlet matches them. /* will match anything after /, but the * will still be available. It's the leading / in his RequestMapping that is missing.

Bernard Hauzeur Over a year ago

Although I like it, the explanation above isn't fully correct and I think there are issues with using * in <url-pattern>'s. I only get the stuff working predictably with a single <url-pattern>/</url-pattern> in web.xml, and then all request mappings starting with /... e.g. /activate/{key}, etc. A set of <url-pattern>'s as allowed by the web.xml schema works predictably only if it does contain no path with * and the controller has an exactly matching set of request mapping paths. Anything else I tried yields errors for what shall be matching patterns.

Steven Hood · Accepted Answer · 2013-03-28 14:14:05Z

1

All of the request mapping I've seen has used a leading slash. Have you tried this: @RequestMapping("/activate/{key}")

answered Mar 28, 2013 at 14:14

Steven Hood

6885 silver badges18 bronze badges

Collectives™ on Stack Overflow

Matching URL pattern with @RequestMapping

3 Answers 3

2 Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related