@PostMapping: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 19: | Line 19: | ||
=REST= | =REST= | ||
<syntaxhighlight lang='java'> | |||
@PostMapping(consumes = "application/json") | |||
@ResponseStatus(HttpStatus.CREATED) | |||
public A post(@RequestBody A a) { | |||
content.put(a.getId(), a); | |||
return a; | |||
} | |||
</syntaxhighlight> | |||
==HTTP POST Semantics for REST Applications== | ==HTTP POST Semantics for REST Applications== |
Revision as of 20:33, 12 March 2019
Internal
Overview
Designates a controller handler method to handle POST requests. The annotation may also contain a sub-path relative to the class-level base path, usually configured with @RequestMapping.
The content of the posted HTML form is presented to the method as a domain model data object: when the form is submitted, the fields in the form are bound to properties of the domain model object instance. In the example below, the form is used to build a taco composition:
@PostMapping
public String processFormContent(Taco taco) {
// ...
return "redirect:/orders/current";
}
REST
@PostMapping(consumes = "application/json")
@ResponseStatus(HttpStatus.CREATED)
public A post(@RequestBody A a) {
content.put(a.getId(), a);
return a;
}
HTTP POST Semantics for REST Applications
Data Members
consume
Specifies what kind of content type(s) the handler is capable of handling.