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.

Related Content you might be interested in

Current Title:

Small book image
Digital Java EE 7 Web Application Development
Peter Pilgrim
Sep, 2015 | 486 pages
No titles found
Table of Contents (21 chapters)
Digital Java EE 7 Web Application Development
Digital Java EE 7 Web Application Development
Credits
Credits
About the Author
About the Author
Acknowledgment
Acknowledgment
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Digital Java EE 7
Digital Java EE 7
Working in the digital domain
Digital Java developer requirements
Java in the picture
The impressive growth of JavaScript
Information architecture and user experience
Java EE 7 architecture
Xentracker JavaServer Faces
Application servers
Summary
Exercises
2
JavaServer Faces Lifecycle
JavaServer Faces Lifecycle
Introduction to JSF
The MVC design pattern
Facelets
The request processing lifecycle
A basic JSF example
A Composition example
Expression language
Page navigation
Summary
Exercises
3
Building JSF Forms
Building JSF Forms
Create, Retrieve, Update, and Delete
JSF custom tags
Displaying a list collection of objects
Editing data
Removing data
JSF and CDI scopes
Summary
Exercises
4
JSF Validation and AJAX
JSF Validation and AJAX
Validation methods
Faces messages
Validation
A partial JSF lifecycle
Handling views
Summary
Exercises
5
Conversations and Journeys
Conversations and Journeys
Digital e-commerce applications
Conversational scope
The conversation scope controller
Page views
Composite custom components
Summary
Exercises
6
JSF Flows and Finesse
JSF Flows and Finesse
What is Faces Flow?
Flow definitions and lifecycle
Simple Implicit Faces Flows
Handling view expired
Declarative and nested flows
A real-world example
Resource Library Contracts
Advice for flows
Summary
Exercises
7
Progressive JavaScript Frameworks and Modules
Progressive JavaScript Frameworks and Modules
JavaScript essentials
Introducing the jQuery framework
The RequireJS framework
UnderscoreJS
GruntJS
Summary
Exercises
8
AngularJS and Java RESTful Services
AngularJS and Java RESTful Services
Single-page applications
The caseworker application
AngularJS
Caseworker overview
Project organization
Application main controller
New case record controller
New task record controller
State change
Server-side Java
Consider your design requirements
Summary
Exercises
9
Java EE MVC Framework
Java EE MVC Framework
Java EE 8 MVC
MVC controllers
Handlebars Java
Design considerations
Summary
Exercises
JSF with HTML5, Resources, and Faces Flows
JSF with HTML5, Resources, and Faces Flows
An HTML5 friendly markup
Resource identifiers
Resource Library Contracts
A Faces servlet
Internationalization
A web deployment descriptor
Programmatic Faces Flows
The Faces Flows programmatic interface
From Request to Response
From Request to Response
HTTP
Java Enterprise Architectures
To be full stack or not
Agile Performance – Working inside Digital Teams
Agile Performance – Working inside Digital Teams
Digital teams and adaptation
Roles
Software quality
Class versus form
Curated References
Curated References
Service delivery
Agile and leadership
Architecture
User interface
Java EE and JVM technology
Index
Index

Resource Library Contracts

JSF 2.2 introduces the concept of Resource Library Contracts, which allows a digital developer to organize a library of assets and templates in a reusable set of resources. A resource library contract must reside in the contracts directory folder in the application's web context root. In the standard Maven or Gradle build convention, this folder is src/main/webapp/contracts. Each subfolder in the contracts folder represents a named resource contract.

The setup for the Chapter 6, JSF Flows and Finesse used a layout for the Resource Library Contracts, as follows:

/src/main/webapp/contracts/

/src/main/webapp/contracts/default/

/src/main/webapp/contracts/default/template.xhtml

/src/main/webapp/contracts/default/styles/app.css

/src/main/webapp/contracts/default/images/

/src/main/webapp/contracts/victoria/

/src/main/webapp/contracts/victoria/template.xhtml

/src/main/webapp/contracts/victoria/styles/app.css

/src/main/webapp/contracts/victoria/images/

Every contract must have at least one declared template.xhtml file. A contract may have more than one template for its own customization. The declared template has at least one declared insertion point, which is defined as the <ui:insert> tag. A template usually relies on the digital assets, and these are known as declared resources.

Contracts can be packaged in the JAR files for a customer's use. A resource library contract must be placed in the META-INF/contracts folder of the JAR file. So, we could repackage the flow examples in the following layout:

META-INF/contracts/

META-INF/contracts/default/javax.faces.contract.xml

META-INF/contracts/default/template.xhtml

META-INF/contracts/default/styles/app.css

META-INF/contracts/default/images/

META-INF/contracts/victoria/

META-INF/contracts/victoria/javax.faces.contract.xml

META-INF/contracts/victoria/template.xhtml

META-INF/contracts/victoria/styles/app.css

META-INF/contracts/victoria/images/

We will need to add an empty marker file to each contract, javax.faces.contract.xml. The reference for this filename is found in the static string: javax.faces.application.ResourceHandler.RESOURCE_CONTRACT_XML.

Previous Section
End of Section
Next Section