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

Developing our first Faces application

To illustrate basic Jakarta Faces concepts, we will develop a simple application consisting of two Facelet pages and a single Contexts and Dependency Injection (CDI) named bean.

Facelets

As we mentioned in this chapter’s introduction, the default view technology for Jakarta Faces is called Facelets. Facelets need to be written using standard XML. The most popular way of developing Facelet pages is to use XHTML in conjunction with Jakarta Faces-specific XML namespaces. The following example shows what a typical Facelet page looks like:

<!-- XML declaration and doctype omitted -->
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:h="jakarta.faces.html"
   xmlns:f="jakarta.faces.core">
  <h:head>
    <title>Enter Customer Data</title>
  </h:head>
  <h:body>
 ...