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

Data modeling framework


All of the data sources are declared as JNDI resources at the Tomcat level. They are declared as Bitronix data sources managed by BitronixTransactionManager. At the Spring context level, all data access is wrapped by JPA using the Hibernate 4.x Framework. BitronixTransactionManager is auto fetched and injected by Spring as its JTA manager to manage all JPA services for any of the data sources. The following figure shows the JTA and JPA setup with multiple data sources:

Multiple JNDI data sources

The persistence.xml file contains five persistence units wherein each is configured to fetch its XA-based data source through the JTA transaction manager. Each persistence unit must know that they are all JNDI data sources managed by the Bitronix transaction manager.

Each persistence unit is mapped to their respective EntityManagerFactory, JPA vendor adapter, and JNDI mappings. For more details on JTA-managed data sources, Chapter 7, Online Cart System (OCS), has all the codes...