Book Image

Apache MyFaces 1.2 Web Application Development

Book Image

Apache MyFaces 1.2 Web Application Development

Overview of this book

Hypes and trends (such as Web 2.0) cause a change in the requirements for user interfaces every now and then. While a lot of frameworks are capable of meeting those changing requirements, it often means you as a developer need in-depth knowledge of web standards, such as XHTML and JavaScript. A framework like Apache MyFaces that hides all details of how the page is rendered at the client and at the same time offers a rich set of tools and building blocks could save you a lot of time, not only when you're building a brand new application but also when you're adapting an existing application to meet new user interface requirements.This book will teach you everything you need to know to build appealing web interfaces with Apache MyFaces and maintain your code in a pragmatic way. It describes all the steps that are involved in building a user interface with Apache MyFaces. This includes building templates and composition components with Facelets, using all sorts of specialized components from the Tomahawk, Trinidad, and Tobago component sets and adding validation with MyFaces Extensions Validator.The book uses a step-by-step approach and contains a lot of tips based on experience of the MyFaces libraries in real-world projects. Throughout the book an example scenario is used to work towards a fully functional application when the book is finished.This step-by-step guide will help you to build a fully functional and powerful application.
Table of Contents (22 chapters)
Apache MyFaces 1.2
Credits
About the Author
Acknowledgement
About the Reviewers
Preface
Trinidad Tags
Trinidad Text Keys
Default JSF Error Messages
ExtVal Default Error Messages

The Model-View-Controller architecture


It is a common practice to implement the Model-View-Controller (MVC) design pattern in a Java EE application. In fact, parts of the Java EE standard are designed around this pattern. The goal of the MVC pattern is to separate business logic from the user interface. The MVC pattern splits an application into three separate parts, each with its own responsibilities, as follows:

  • Model: This part is responsible for manipulating application data. In other words, the Model implements the business logic.

  • View: This part is responsible for presenting the contents of the Model to the user, and providing ways for the user to send data or commands to the application.

  • Controller: This part defines the behavior of the application, and is responsible for receiving the user’s input.

So far in this book, we have only created a view and a controller for an application. In a JSF-based application, the View consists of all of the JSP or Facelets pages. The JSF Controller...