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
Java EE 8 Application Development

You're reading from   Java EE 8 Application Development Develop Enterprise applications using the latest versions of CDI, JAX-RS, JSON-B, JPA, Security, and more

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781788293679
Length 372 pages
Edition 1st Edition
Languages
Tools
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 (15) Chapters Close

Preface 1. Introduction to Java EE FREE CHAPTER 2. JavaServer Faces 3. Object Relational Mapping with the Java Persistence API 4. Enterprise JavaBeans 5. Contexts and Dependency Injection 6. JSON Processing with JSON-P and JSON-B 7. WebSocket 8. Java Messaging Service 9. Securing Java EE Applications 10. RESTful Web Services with JAX-RS 11. Microservices Development with Java EE 12. Web Services with JAX-WS 13. Servlet Development and Deployment 14. Configuring and Deploying to GlassFish

JSF 2.2 Faces flows


JSF 2.2 introduced Faces flows, which 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 JSF. 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

The following screenshot illustrates these conventions:

In the preceding example...

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