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
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Java EE 7 Web Application Development

You're reading from   Java EE 7 Web Application Development Develop Java enterprise applications to meet the emerging digital standards using Java EE 7

Arrow left icon
Product type Paperback
Published in Sep 2015
Publisher
ISBN-13 9781782176640
Length 486 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Peter Pilgrim Peter Pilgrim
Author Profile Icon Peter Pilgrim
Peter Pilgrim
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Digital Java EE 7 FREE CHAPTER 2. JavaServer Faces Lifecycle 3. Building JSF Forms 4. JSF Validation and AJAX 5. Conversations and Journeys 6. JSF Flows and Finesse 7. Progressive JavaScript Frameworks and Modules 8. AngularJS and Java RESTful Services 9. Java EE MVC Framework A. JSF with HTML5, Resources, and Faces Flows B. From Request to Response C. Agile Performance – Working inside Digital Teams D. Curated References Index

Simple Implicit Faces Flows


It is relatively straightforward to create an Implicit Faces Flow with just a folder name, an empty XML configuration, and some Facelet pages. A flow is a folder name in your web application, preferably at the root directory. We start with the basic flow in the directory of the same name called digitalFlow. Your flow must match the name of the folder.

In order to define an implicit flow, we create an empty XML file with the common basename and a suffix: digitalFlow/digitalFlow-flow.xhtml.

We now create a start page in the folder with the common basename. This file is a Facelet view page called digitalFlow/digitalFlow.xhtml.

We can create other pages in the flow inside the folder, and they can have any name we like. We might have digitalFlow/digitalFlow1.xhtml, digitalFlow/checkout.xhtml, or digitalFlow/song.xhtml. Only the defined flow digitalFlow can ever access these pages. If an outside call does attempt to access any of these pages, the JSF implementation will...

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