Book Image

Developing Middleware in Java EE 8

Book Image

Developing Middleware in Java EE 8

Overview of this book

Middleware is the infrastructure in software based applications that enables businesses to solve problems, operate more efficiently, and make money. As the use of middleware extends beyond a single application, the importance of having it written by experts increases substantially. This book will help you become an expert in developing middleware for a variety of applications. The book starts off by exploring the latest Java EE 8 APIs with newer features and managing dependencies with CDI 2.0. You will learn to implement object-to-relational mapping using JPA 2.1 and validate data using bean validation. You will also work with different types of EJB to develop business logic, and with design RESTful APIs by utilizing different HTTP methods and activating JAX-RS features in enterprise applications. You will learn to secure your middleware with Java Security 1.0 and implement various authentication techniques, such as OAuth authentication. In the concluding chapters, you will use various test technologies, such as JUnit and Mockito, to test applications, and Docker to deploy your enterprise applications. By the end of the book, you will be proficient in developing robust, effective, and distributed middleware for your business.
Table of Contents (18 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Injecting the validator object


Recalling the first approach, and rather than programmatically creating the validator object by creating a ValidatorFactory using the Validation class and so on, you can simply inject the Validator object as a dependency using the CDI, as shown in the following example:

@RequestScoped 
public class MovieBean { 
 
    @PersistenceContext(name = "jpa-examplesPU") 
    private EntityManager entityManager; 
    @Inject 
    private Validator validator; 
 
    public void validateMovie() { 
 
        Movie movie = new Movie(); 
 
        Set<ConstraintViolation<Movie>> violations = validator.validate(movie); 
        for (ConstraintViolation<Movie> violation : violations) { 
            System.out.println(violation.getPropertyPath()); 
            System.out.println(violation.getMessage()); 
        } 
    } 
} 

As you see, the validator object is injected as a dependency rather than having to create it with many lines of code. There will be cases...