原文地址：
@RequestMapping is one of the most widely used Spring MVC annotation.org.springframework.web.bind.annotation.RequestMapping annotation is used to map web requests onto specific handler classes and/or handler methods.
@RequestMapping can be applied to the controller class as well as methods. Today we will look into various usage of this annotation with example.
- @RequestMapping with Class: We can use it with class definition to create the base URI. For example:
12
3
4
5
@Controller@RequestMapping("/home")publicclassHomeController {}Now /home is the URI for which this controller will be used. This concept is very similar to servlet context of a web application.
- @RequestMapping with Method: We can use it with method to provide the URI pattern for which handler method will be used. For example:
12
3
4
5
@RequestMapping(value="/method0")@ResponseBodypublicString method0(){return"method0";}Above annotation can also be written as
@RequestMapping("/method0"). On a side note, I am using @ResponseBody to send the String response for this web request, this is done to keep the example simple. Like I always do, I will use these methods in Spring MVC application and test them with a simple program or script. - @RequestMapping with Multiple URI: We can use a single method for handling multiple URIs, for example:
12
3
4
5
@RequestMapping(value={"/method1","/method1/second"})@ResponseBodypublicString method1(){return"method1";}If you will look at the source code of RequestMapping annotation, you will see that all of it’s variables are arrays. We can create String array for the URI mappings for the handler method.
- @RequestMapping with HTTP Method: Sometimes we want to perform different operations based on the HTTP method used, even though request URI remains same. We can use @RequestMapping method variable to narrow down the HTTP methods for which this method will be invoked. For example:
12
3
4
5
6
7
8
9
10
11
@RequestMapping(value="/method2", method=RequestMethod.POST)@ResponseBodypublicString method2(){return"method2";}@RequestMapping(value="/method3", method={RequestMethod.POST,RequestMethod.GET})@ResponseBodypublicString method3(){return"method3";} - @RequestMapping with Headers: We can specify the headers that should be present to invoke the handler method. For example:
12
3
4
5
6
7
8
9
10
11
@RequestMapping(value="/method4", headers="name=pankaj")@ResponseBodypublicString method4(){return"method4";}@RequestMapping(value="/method5", headers={"name=pankaj","id=1"})@ResponseBodypublicString method5(){return"method5";} - @RequestMapping with Produces and Consumes: We can use header
Content-TypeandAcceptto find out request contents and what is the mime message it wants in response. For clarity, @RequestMapping provides produces and consumes variables where we can specify the request content-type for which method will be invoked and the response content type. For example:
12
3
4
5
@RequestMapping(value="/method6", produces={"application/json","application/xml"}, consumes="text/html")@ResponseBodypublicString method6(){return"method6";}Above method can consume message only with Content-Type as text/html and is able to produce messages of type application/json and application/xml.
- @RequestMapping with @PathVariable: RequestMapping annotation can be used to handle dynamic URIs where one or more of the URI value works as a parameter. We can even specify Regular Expression for URI dynamic parameter to accept only specific type of input. It works [email protected] annotation through which we can map the URI variable to one of the method arguments. For example:
12
3
4
5
6
7
8
9
10
11
@RequestMapping(value="/method7/{id}")@ResponseBodypublicString method7(@PathVariable("id")intid){return"method7 with id="+id;}@RequestMapping(value="/method8/{id:[\\d]+}/{name}")@ResponseBodypublicString method8(@PathVariable("id")longid,@PathVariable("name") String name){return"method8 with id= "+id+" and name="+name;} - @RequestMapping with @RequestParam for URL parameters: Sometimes we get parameters in the request URL, mostly in GET requests. We can use @RequestMapping with @RequestParam annotationto retrieve the URL parameter and map it to the method argument. For example:
12
3
4
5
@RequestMapping(value="/method9")@ResponseBodypublicString method9(@RequestParam("id")intid){return"method9 with id= "+id;}For this method to work, the parameter name should be “id” and it should be of type int.
- @RequestMapping default method: If value is empty for a method, it works as default method for the controller class. For example:
12
3
4
5
@RequestMapping()@ResponseBodypublicString defaultMethod(){return"default method";}As you have seen above that we have mapped
/hometoHomeController, this method will be used for the default URI requests. - @RequestMapping fallback method: We can create a fallback method for the controller class to make sure we are catching all the client requests even though there are no matching handler methods. It is useful in sending custom 404 response pages to users when there are no handler methods for the request.
12
3
4
5
@RequestMapping("*")@ResponseBodypublicString fallbackMethod(){return"fallback method";}
Test Program
We can use Spring RestTemplate to test the different methods above, but today I will use cURL commands to test these methods because these are simple and there are not much data flowing around.
I have created a simple shell script to invoke all the above methods and print their output. It looks like below.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 |
|
Note that I have deployed my web application on Tomcat-7 and it’s running on port 9090.SpringRequestMappingExample is the servlet context of the application. Now when I execute this script through command line, I get following output.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 |
|
Most of these are self understood, although you might want to check default and fallback methods. That’s all for Spring RequestMapping Example, I hope it will help you in understanding this annotation and it’s various features. You should download the sample project from below link and try different scenarios to explore it further.