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

Final notes

In the examples for this chapter, we demonstrated database access directly from CDI named beans serving as controllers. We did this to get the point across without bogging ourselves down with details; however, in general, this is not a good practice. Database access code should be encapsulated in Data Access Objects (DAOs).

DAO design pattern

For more information on the DAO design pattern, see http://www.oracle.com/technetwork/java/dao-138818.html.

Named beans typically assume the role of controllers and/or models when using the Model-View-Controller (MVC) design pattern, a practice so common that it has become a de-facto standard for Jakarta EE applications.

MVC design pattern

For more information about the MVC design pattern, see https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller.

Additionally, we chose not to show any user interface code in our examples as it was irrelevant to the topic at hand. However, the code downloads for this...