Book Image

Digital Java EE 7 Web Application Development

By : Peter Pilgrim
Book Image

Digital Java EE 7 Web Application Development

By: Peter Pilgrim

Overview of this book

Digital Java EE 7 presents you with an opportunity to master writing great enterprise web software using the Java EE 7 platform with the modern approach to digital service standards. You will first learn about the lifecycle and phases of JavaServer Faces, become completely proficient with different validation models and schemes, and then find out exactly how to apply AJAX validations and requests. Next, you will touch base with JSF in order to understand how relevant CDI scopes work. Later, you’ll discover how to add finesse and pizzazz to your digital work in order to improve the design of your e-commerce application. Finally, you will deep dive into AngularJS development in order to keep pace with other popular choices, such as Backbone and Ember JS. By the end of this thorough guide, you’ll have polished your skills on the Digital Java EE 7 platform and be able to creat exiting web application.
Table of Contents (21 chapters)
Digital Java EE 7 Web Application Development
Credits
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
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...