Book Image

JSF 1.2 Components

By : IAN HLAVATS
Book Image

JSF 1.2 Components

By: IAN HLAVATS

Overview of this book

Today's web developers need powerful tools to deliver richer, faster, and smoother web experiences. JavaServer Faces includes powerful, feature-rich, Ajax-enabled UI components that provide all the functionality needed to build web applications in a Web 2.0 world. It's the perfect way to build rich, interactive, and "Web 2.0-style" Java web apps. This book provides a comprehensive introduction to the most popular JSF components available today and demonstrate step-by-step how to build increasingly sophisticated JSF user interfaces with standard JSF, Facelets, Apache Tomahawk/Trinidad, ICEfaces, JBoss Seam, JBoss RichFaces/Ajax4jsf, and JSF 2.0 components. JSF 1.2 Components is both an excellent starting point for new JSF developers, and a great reference and “how to” guide for experienced JSF professionals. This book progresses logically from an introduction to standard JSF HTML, and JSF Core components to advanced JSF UI development. As you move through the book, you will learn how to build composite views using Facelets tags, implement common web development tasks using Tomahawk components, and add Ajax capabilities to your JSF user interface with ICEfaces components. You will also learn how to solve the complex web application development challenges with the JBoss Seam framework. At the end of the book, you will be introduced to the new and up-coming JSF component libraries that will provide a road map of the future JSF technologies.
Table of Contents (14 chapters)
JSF 1.2 Components
Credits
Foreword
About the Author
About the Reviewers
Preface

Skinning and theme selection


One of the most powerful and interesting features of the Trinidad framework is its support for customizing the appearance of a wide range of user interface elements through the use of a coordinated set of cascading style sheets, images, and other presentational resources.

Different themes can be created and declared as "skins" for the application in a centralized XML file named /WEB-INF/trinidad-skins.xml. The current skin for the application can be hardcoded in the /WEB-INF/trinidad-config.xml file, or it can be determined at runtime based on stored user preferences, a predefined schedule, or any other criteria. Additionally, custom Trinidad skins can be defined in a JAR file, enabling them to be reused more easily.

In our demonstration, we declare the skin family as an EL expression bound to a sessionScope variable named skinFamily. (This session variable has no special meaning in Trinidad and is not created by default; it is simply used here to demonstrate...