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

Transaction management using JTA


The three project versions of this chapter use JTA as the transaction manager, just in case the system gets huge scope implementing more than one data source. Previous chapters highlighted that Spring MVC 4.x uses JDBC as the interface to connect to databases and were also successful in implementing the JPA entity manager that uses @PersistenceContext for in-memory collection of entities, which isolates the application from the inner workings of JDBC and database operations. Any CRUD done in the entities automatically updates the tables in the databases.

However, this chapter implements JTA allowing OCS for management of multiple transactions among multiple databases in the future. It is still JPA which will utilize the JDBC connections and SQL-related operations, but with the option, now, of utilizing JTA for delegating distributed transaction management, once databases are added to accommodate numerous records. OCS will only have one data source despite...