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

Summary

In this chapter, we provided an introduction to CDI, an integral part of the Jakarta EE specification. We looked into the following:

  • We covered how Jakarta Faces pages can access CDI-named beans via the unified expression language.
  • We also covered how CDI makes it easy to inject dependencies into our code via the @Inject annotation.
  • Additionally, we explained how we can use qualifiers to determine what specific implementation of a dependency to inject into our code.
  • We also discussed all the scopes that a CDI bean can be placed into, allowing us to delegate the life cycle of CDI beans to the Jakarta EE runtime.
  • We discussed how to implement loosely coupled communication between CDI beans via CDI’s event handling.
  • Lastly, we discussed CDI Lite, a lightweight version of CDI suitable for microservices development.

CDI is an integral part of Jakarta EE, as it is used to integrate different layers of our Jakarta EE applications.