Introducing Spring Framework

Chapter 12 ■ Exposing a REST API
}
@RequestMapping(value="/{id}",method=RequestMethod.DELETE)
public @ResponseBody Document removeDocument(@PathVariable String id){
return documentFacade.removeDocumentById(id);
}
Remember Chapter 10? You are doing the same thing here, defining the controller through the different
annotations. The Spring Framework MVC extension facilitates the way you expose these resources or web services.
The difference now is that you are using the @ResponseBody and @RequestBody annotations. The Spring MVC
extension uses JSON (JavaScript Object Notation, a readable text format with key-value pairs) as the default format
for the RESTful resources, so @ResponseBody will convert the result in a JSON format and @RequestBody will accept a
Content-Type:"application/json" format. Also, you are using the @PathVariable that will match the variable name
between curly braces and the name of the parameter within the method call.
Listing 12-5 shows the XML configuration that you will use in the unit test. The web.xml is the same as the one in
Chapter 10.
Listing 12-5. WEB-INF/mydocuments-servlet.xml
175