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

Configuring Jakarta Persistence

Jakarta Persistence requires a bit of configuration before our code can work properly. A data source needs to be defined. The data source specifies information on how to reach the Relational Database Management System (RDBMS) system we are connecting to (server, port, database user credentials, etc.). There are two ways it can be set up. It can be done via the Jakarta EE implementation configuration, but how to do this is dependent on the specific implementation.

It can also be done by annotating an application-scoped CDI bean via the @DataSourceDefinition annotation.

There are advantages and disadvantages to each approach. Defining the data source as part of the Jakarta EE runtime configuration allows us to deploy our code to different environments (development, test, production) without having to make any modifications to our code. It also prevents adding any user credentials to our source. Using @DataSourceDefinition works across Jakarta EE...