What is the difference between @RequestMapping and @PostMapping
From the @PostMapping
docs :
Specifically, @PostMapping is a composed annotation that acts as a shortcut for @RequestMapping(method = RequestMethod.POST).
So it is only convenience annotation that is more "verbose" and indicates that method annotated with it is used for handling POST HTTP requests.
I have just checked your controller methods with 2.1.4
spring boot version and your scenarios work as expected so there has to be something wrong in your configuration or the way you are sending requests.
Related videos on Youtube
user2121
Updated on September 28, 2022Comments
-
user2121 over 1 year
in the below example, I am trying to undersatnd the difference between @RequestMapping and @PostMapping. For @RequestMapping:
when i do the POST request: http://localhost:8085/call1/initparam1?val=1111 via postman, it executes correctly. but when its is proceeded by by GET request
http://localhost:8085/call1/getparam1i do not get 1111 as a result.
For @PostMapping, when i do the POST request: http://localhost:8085/call1/initparam2/1999 via postman, it executes correctly. but when its is proceeded by by GET request
http://localhost:8085/call1/getparam1i do not get 1999 as a result.
please explain to me what is the difference between using both annotations, as i spent time googling and researching but i could not figure out why the first example is not working.
Controller1
@Controller @ResponseBody @RequestMapping("/call1") public class Call1 { public String str = "inti"; @RequestMapping(value = "/initparam1", method = RequestMethod.POST) public void initparam1(@RequestParam(value = "val") String val) { this.str = val; } @PostMapping(value = "/initparam2/{val}") public void initparam2(@PathVariable String val) { this.str = val; } @RequestMapping("/getparam1") @ResponseBody public String getParam1() { return this.str; } }
-
user2121 almost 5 yearsbut did you realized the other part of the quest. please. using the POSTMAPPING gives me the expected result but the REQUESTMAPPING gives unexpected result
-
Michał Krzywański almost 5 yearsI have just checked your set up and it works as expected, both endpoints set the value of your String.