Book Image

Spring MVC Cookbook

By : Alexandre Bretet, Alex Bretet
Book Image

Spring MVC Cookbook

By: Alexandre Bretet, Alex Bretet

Overview of this book

Spring MVC is a lightweight application framework that comes with a great configuration by default. Being part of the Spring Framework, it naturally extended and supported it with an amazing set of recognizable annotations. External libraries can be plugged in and plugged out. It also possesses a request flow. Complete support of REST web services makes the Spring architecture an extremely consistent choice to support your front-end needs and Internet transformations. From the design of your Maven modules, you will achieve an Enterprise-standard for a stateless REST application based on Spring and Spring MVC with this book. This guide is unique in its style as it features a massive overview of practical development techniques brought together from the Spring ecosystem, the new JEE standards, the JavaScript revolution and Internet of Things. You will begin with the very first steps of Spring MVC's product design. Focused on deployment, viability, and maintainability, you will learn the use of Eclipse, Maven, and Git. You will walk through the separation of concerns driven by the microservices principles. Using Bootstrap and AngularJS, you will develop a responsive front-end, capable of interacting autonomously with a REST API. Later in the book, you will setup the Java Persistence API (JPA) within Spring; learn how to configure your Entities to reflect your domain needs, and discover Spring Data repositories. You will analyze how Spring MVC responds to complex HTTP requests. You will implement Hypermedia and HATEOAS to guide your customer's stateless conversation with the product and see how a messaging-service based on WebSocket can be configured. Finally you will learn how to set up and organize different levels of automated-tests, including logging and monitoring.
Table of Contents (16 chapters)
Spring MVC Cookbook
About the Author
About the Reviewer


As we are now approaching the end of this journey, we must see how to consolidate the work. In the real world, tests must be written before a feature is developed (or at least at the same time). Writing automated tests in software development conveys a massive confidence about the application state. It is the best way of ensuring that nothing has been forgotten. Having a system that has the ability to test itself, with the help of modern continuous integration tools, ensures that features will not be damaged at any time.

Manual testing through UI cannot be trusted to cover every single edge case that a developer has to think about. It is the responsibility of the developer to secure all the breaches and to cover all the possible paths, and this is a big responsibility.

Our developer job is an amazing job. The perpetual technology enhancement sets an incomparable pace for every one of us—to stay in the race, to respond to the market, and sometimes to lead the market.

Our job is...