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

CDI Lite

The Jakarta EE Core Profile contains a subset of the full CDI specification, named, appropriately enough, CDI Lite. Most of the changes of CDI Lite are at the implementation level; namely, some functionality that the full CDI implementation performs at runtime is moved to build time, allowing applications utilizing CDI Lite to initialize faster.

CDI Lite is primarily meant to be used in microservices applications, implementing functionality as RESTful web services. Since REST applications are typically stateless, not all CDI scopes are applicable when working on this type of application. For this reason, the session and conversation scopes are not available when using CDI Lite. This is the primary limitation of CDI Lite when compared to the full CDI specification.

We only need to be concerned with CDI Lite limitations when deploying our code to a Jakarta EE Core Profile implementation. The Jakarta EE Web Profile and the full Jakarta EE platform contain full CDI functionality...