The REST with Spring series discusses the process of building a RESTful web service with Spring. It deals with the MVC Spring configuration, looks at Java based configuration without any XML, Discoverability and HATEOAS, Security (From, Basic and Digest authentication), Integration Testing and other areas in the context of REST.
This article focuses on bootstrapping the web application, also discussing how to make the jump from XML to Java without having to completely migrate the entire XML configuration.
This article focuses on setting up REST in Spring, the Controller and HTTP response codes, configuration of payload marshalling and content negotiation.
The article focuses on Discoverability of the RESTful service, HATEOAS and some practical scenarios driven by tests.
This article focuses on the actual implementation of discoverability and satisfying the HATEOAS constraint in the REST Service using Spring 3.1.
This article shows how to implement pagination in a RESTful web service.
This article shows how to set up authentication with Spring Security against a RESTful web service.
This article will focus on how to implement Exception Handling with Spring for a REST API. We’ll look at the older solutions available before Spring 3.2 and then at the new Spring 3.2 support.
This article will focus on testing a RESTful Service with multiple Media Types/representations.
This article focuses on the security configuration using Spring Security 3.1.
This article focuses on configuration of Basic and Digest authentication and on configuring both protocols for the same URI mapping of the API, using Spring Security 3.1.
This article shows how to set up Authentication with Spring Security against a RESTful web service.
This article will focus on how to consume a REST API secured with Basic Authentication using the RestTemplate and HttpClient 4.
The entire series in based on this github project. Watch and fork it at will – the project can be used as a starting point for a more full fledged implementation.
P.S. If you read this far, you should follow me on Twitter.