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

Chapter 4. Validating Data with Bean Validation 2.0

Validating data is one of the most common and important operations in an enterprise solution. Whatever your application domain is, you should always validate your data against the proposed business constraints, and in the different layers of your application. You should always validate data entered directly by the user (in the presentation layer), data received by your web services, data received by your business objects, and data before being sent to the database (in the data access layer).

But why you should validate your data in all application layers rather than the presentation layer, which has direct contact with your end user? 

The answer is this: you may expose a web service layer to allow integration with third parties, or even have a set of web services to support your frontend without an intent to expose them to third parties, and still a hacker can find a way to call your services in a way that violates your business constraints...