Book Image

Seam 2.x Web Development

Book Image

Seam 2.x Web Development

Overview of this book

The Seam framework from JBoss allows developers to use JSF, Facelets, EJB, and JPA to write conversational web applications. But you will first have to learn how these standard technologies are integrated using Seam and how they can be built upon using additional Seam components. If you need to build a Java web application fast, but don't have time to learn all these complex features, then this book is for you. The book provides a practical approach to developing Seam applications highlighting good development practices. It provides a complete walk through to develop Web applications using Seam, Facelets, and RichFaces and explains how to deploy them to the JBoss Application Server. You can start using key aspects of the Seam framework immediately because this book builds on them chapter by chapter, finally ending with details of enterprise functionality such as PDF report generation and event frameworks. First, the book introduces you to the fundamentals of Seam applications, describing topics such as Injection, Outjection and Bijection. You will understand the Facelets framework, AJAX, database persistence, and advanced Seam concepts through the many examples in the book. The book takes a practical approach throughout to describing the technologies and tools involved. You will add functionality to Seam applications after you learn how to use the Seam Generator RAD tools and how to customize and fully test application functionality. Hints and tips are provided along the way of how to use Seam and the JBoss Application Server.
Table of Contents (17 chapters)
Seam 2.x Web Development
Credits
About the author
About the reviewers
Preface

OpenID


If you want to use a security mechanism in your applications, but don't want to be responsible for managing lists of users and passwords, then OpenID may be the answer.

OpenID is an open standard authentication scheme that allows users to log onto many different web sites using the same identity on each of the web sites. There are many different providers of OpenID (for example, Google, Yahoo!, and so on), and also many different web sites that allow users to authenticate using OpenID (http://dzone.com, http://livejournal.com, http://sourceforge.net, and so on). When a user logs on to an OpenID-enabled application, they are redirected to their OpenID provider for authentication. If the user authenticates correctly with their OpenID provider, they are redirected back to the originating application and are automatically authenticated. Using a provider for authentication removes the need for all of the authentication code within a web application, as this is all managed by the OpenID...