Book Image

Spring MVC Blueprints

By : Sherwin John C. Tragura
Book Image

Spring MVC Blueprints

By: Sherwin John C. Tragura

Overview of this book

Spring MVC is the ideal tool to build modern web applications on the server side. With the arrival of Spring Boot, developers can really focus on the code and deliver great value, leveraging the rich Spring ecosystem with minimal configuration. Spring makes it simple to create RESTful applications, interact with social services, communicate with modern databases, secure your system, and make your code modular and easy to test. It is also easy to deploy the result on different cloud providers. This book starts all the necessary topics in starting a Spring MVC-based application. Moving ahead it explains how to design model objects to handle file objects. save files into a data store and how Spring MVC behaves when an application deals with uploading and downloading files. Further it highlights form transactions and the user of Validation Framework as the tool in validating data input. It shows how to create a customer feedback system which does not require a username or password to log in. It will show you the soft side of Spring MVC where layout and presentation are given importance. Later it will discuss how to use Spring Web Flow on top of Spring MVC to create better web applications. Moving ahead, it will teach you how create an Invoice Module that receives and transport data using Web Services By the end of the book you will be able to create efficient and flexible real-time web applications using all the frameworks in Spring MVC.
Table of Contents (16 chapters)
Spring MVC Blueprints
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

The concept of web services


The ERP prototype showcased in this chapter provides a profound and detailed pedagogy on how to set up web services given a Spring 4.x platform. The conceptual model is to create an ERP wherein all modules are scattered into different islands of networks or distributed around the network as independent real-time applications that share their results given a set of inputs.

All these applications are designed to communicate with each other through a collection of services. The communication can involve either simple data passing or it could involve two or more services coordinating on some activity.

Consumer-producer relationship

All five modules are purely client modules meaning there are no repository (DAO) or service layers in each of the applications. The data and service layers are found in a central repository module which is responsible for the generation of web services. The service layer is exposed as a set of web services depending on the technology used...