Book Image

Jakarta EE Application Development - Second Edition

By : David R. Heffelfinger
Book Image

Jakarta EE Application Development - Second Edition

By: David R. Heffelfinger

Overview of this book

Jakarta EE stands as a robust standard with multiple implementations, presenting developers with a versatile toolkit for building enterprise applications. However, despite the advantages of enterprise application development, vendor lock-in remains a concern for many developers, limiting flexibility and interoperability across diverse environments. This Jakarta EE application development guide addresses the challenge of vendor lock-in by offering comprehensive coverage of the major Jakarta EE APIs and goes beyond the basics to help you develop applications deployable on any Jakarta EE compliant runtime. This book introduces you to JSON Processing and JSON Binding and shows you how the Model API and the Streaming API are used to process JSON data. You’ll then explore additional Jakarta EE APIs, such as WebSocket and Messaging, for loosely coupled, asynchronous communication and discover ways to secure applications with the Jakarta EE Security API. Finally, you'll learn about Jakarta RESTful web service development and techniques to develop cloud-ready microservices in Jakarta EE. By the end of this book, you'll have developed the skills to craft secure, scalable, and cloud-native microservices that solve modern enterprise challenges.
Table of Contents (18 chapters)
15
Chapter 15: Putting it All Together

Bean Validation support

Bean Validation is a Jakarta EE specification consisting of a number of annotations used to simplify data validation. Jakarta Persistence Bean Validation support allows us to annotate our entities with Bean Validation annotations. These annotations allow us to easily validate user input and perform data sanitation.

Taking advantage of Bean Validation is very simple. All we need to do is annotate our Jakarta Persistence Entity fields or getter methods with any of the validation annotations defined in the jakarta.validation.constraints package. Once our fields are annotated as appropriate, EntityManager will prevent non-validating data from being persisted.

The following code example is a modified version of the Customer Jakarta Persistence entity we saw earlier in this chapter. It has been modified to take advantage of Bean Validation in some of its fields:

package com.ensode.jakartaeebook.beanvalidation.entity;
//imports omitted for brevity
@Entity...