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

Using inline texts


Facelets is, in a lot of ways, more "relaxed" than JSP as a view technology for JSF. One of the ways is the way we can use inline texts. With JSF, you always need a component to render text on the output. This can make our page definitions more complicated than necessary. Facelets will keep the XHTML tags that we mix with our JSF components, and will also retain any plain texts. (This is called content interweaving.) This means that we no longer need JSF components for rendering static elements on a page. We can even incorporate some dynamic or internationalized texts, because Facelets allows us to use Expression Language within inline texts. This means, the quote of the day example from the previous section can be rewritten in a more elegant way, as follows:

<ui:composition template="templates/template.xhtml">
<ui:define name="title">Login</ui:define>
<ui:define name="content">
<h:form id="login">
<h:panelGrid columns="4">
<mias...