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

Introduction to Jakarta Faces

In this section, we will give a general overview of what developing web applications with Jakarta Faces entails, providing some background information necessary before digging into the nitty gritty of Jakarta Faces.

Facelets

Facelets is the default Jakarta Faces view technology. Facelets are written using standard Extensible Hypertext Markup Language (XHTML), using Jakarta Faces-specific XML namespaces that provide Jakarta Faces-specific tags we can use to develop the user interface of our web applications.

Optional faces-config.xml

In most cases, configuring a Jakarta Faces application is not necessary, as it follows a convention over configuration approach.

For some specific cases, when overriding Jakarta Faces’ default error messages for example, we still need to configure Jakarta Faces via a faces-config.xml configuration file.

Standard resource locations

Resources are artifacts a page or Jakarta Faces component needs to...