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
About the Author
About the Reviewers

Java EE 8 MVC

Before we continue on to the programming, I should warn you that the information here is subject to change, because MVC is evolving right in front of our eyes. As an avid reader, you should certainly verify, at least, that the API is with the current or final specification.

With all this said, the MVC framework certainly—even at this early stage—will be a leading specification for the future digital web development framework for many years to come, and not just because it is now officially part of the Java EE umbrella drivetrain. MVC leverages the JAX-RS (Java for RESTful Services) API and currently integrates with the other Java EE technologies including CDI and Bean Validation.

The expert group made the decision to layer on top of JAX-RS rather than the older Java servlet API, because JAX-RS fits the modern programming practice to use full semantics of the HTTP mapping capabilities. They also felt that adopting servlet would expose the developer to the lower-level programming...