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

Setting up Orchestra


This section outlines the steps needed to prepare our project to use MyFaces Orchestra. This involves changing the structure of our application, adding and configuring the Spring framework, and adding the Orchestra libraries.

Adapting the application structure

Orchestra runs in the web application container (the WAR file). To be able to manage transactions in the persistence framework, Orchestra must have access to the persistence classes. (Obviously, this isn’t necessary if we don’t want to use Orchestra’s persistence support.) This means that we can’t put our persistence classes into a separate EJB container. Fortunately, as Orchestra uses Spring, we don’t need an EJB container because Spring is capable of performing the tasks that are typically done by an EJB container. Also, using both Spring and a separate EJB container would make things overly complex.

Of course, putting the persistence and presentation layer in the same container has some down-sides too. For very...