Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Jakarta EE Application Development

You're reading from   Jakarta EE Application Development Build enterprise applications with Jakarta CDI, RESTful web services, JSON Binding, persistence, and security

Arrow left icon
Product type Paperback
Published in Feb 2024
Publisher Packt
ISBN-13 9781835085264
Length 316 pages
Edition 2nd Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
David R. Heffelfinger David R. Heffelfinger
Author Profile Icon David R. Heffelfinger
David R. Heffelfinger
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Chapter 1: Introduction to Jakarta EE FREE CHAPTER 2. Chapter 2: Contexts and Dependency Injection 3. Chapter 3: Jakarta RESTful Web Services 4. Chapter 4: JSON Processing and JSON Binding 5. Chapter 5: Microservices Development with Jakarta EE 6. Chapter 6: Jakarta Faces 7. Chapter 7: Additional Jakarta Faces Features 8. Chapter 8: Object Relational Mapping with Jakarta Persistence 9. Chapter 9: WebSockets 10. Chapter 10: Securing Jakarta EE Applications 11. Chapter 11: Servlet Development and Deployment 12. Chapter 12: Jakarta Enterprise Beans 13. Chapter 13: Jakarta Messaging 14. Chapter 14: Web Services with Jakarta XML Web Services 15. Chapter 15: Putting it All Together 16. Index 17. Other Books You May Enjoy

Faces Flows

Faces Flows defines a scope that can span several pages. Flow-scoped beans are created when the user enters a flow (a set of web pages), and are destroyed when the user leaves the flow.

Faces Flows adopts the convention-over-configuration principle of Jakarta Faces. The following conventions are typically used when developing applications employing Faces Flows:

  • All pages in the flow must be placed in a directory whose name defines the name of the flow.
  • An XML configuration file named after the directory name and suffixed with -flow must exist inside the directory that contains the pages in the flow (the file may be empty, but it must exist)
  • The first page in the flow must be named after the directory name that contains the flow
  • The last page in the flow must not be located inside the directory containing the flow, and must be named after the directory name and suffixed with -return

Figure 7.3 illustrates these conventions:

Figure 7.3: Faces Flows conventions ...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image