This code accompanies a talk that I deliver on RESTful service development with Spring.
The goals of this project are to demonstrate the development of a simple REST service with Spring. The REST service concerns itself with the domain of a simple CRM: a
user manages a
The data tier module
services uses Spring Data JPA repositories, a standard SQL database, and Spring’s standard transaction management infrastructure to build a service. This tier is configured by importing the class
com.jl.crm.services.ServiceConfiguration. Currently there are two Spring profiles. One called
production, which attempts to the SQL database configured in
test, which manages an embedded H2 database which can be accessed at the embedded H2 database console web application with the configuration shown below.
There are four web-tier modules,
oauth, which demonstrate the evolution of a REST service implemented using Spring MVC to manage
customers. The initial cut,
rest, is fairly RESTful, but not HATEOAS and hypermedia compliant. The next cut,
hateoas uses Spring HATEOAS to introduce hypermedia. This improvement, while welcome, is not without an associated cost in code. The next cut,
hateoas-data, introduces Spring Data REST which reduces boilerplate code associated with managing data from the REST endpoint to the database. In the final cut,
oauth, we introduce Spring Security and Spring Security OAuth to secure the API’s from both prying eyes and unauthorized application clients.
social module is a Spring Social API binding for the OAuth 2.0-secured CRM REST API. The
ClientExample demonstrates how to configure and use the Spring Social binding outside of a web container and demonstrates some of its uses.
For a detailed walkthrough of all the code, please check out the tutorial.