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 service layer


Just like with the DAO layer, each implementation type has its own implementation of service classes. But all of the implementations have both org.packt.academic.student.portal.service and  org.packt.academic.student.portal.service.impl packages. The purpose of the business layer is to implement business logic with the use of the DAO objects.

Implementation A – using the Spring JDBC plugin

Given the LoginService interface of the SMP as follows:

public interface LoginService { 
  public boolean isAdminUser(Login login); 
  public boolean isStudentUser(Login login); 
  public boolean isFacultyUser(Login login); 
} 

The implementation of this interface is just a typical Transactional class. A @Transactional class starts with a transaction on each method start, and commits it on each method exit (or rollback, if the method was failed due to an error). Note that since the transactions are in the method's scope, and inside method we are using DAO, the DAO...