0 
0 What seems like a very interesting presentation from the tech lead for JSF:
TheServerSide Java Symposium 2005. The description:
The need for a common API for Java-based web application user interface components was obvious – by the time that the Java Specification Request (JSR) for this API was started, there were over thirty open source and commercial libraries that covered all or part of this functional space. JSF’s goals included gaining consensus on a common API for building interoperable components, but it was also more aggressive in its goals: it was also to be the leading edge of a movement towards making Java APIs easier to use, as well as easier for tools vendors to create high quality design time experiences around that API. We will briefly review the history of JSF, and examine the ecosystem around this API, plus talk about what might be useful in the future.
Related posts:
Apache MyFaces (open source JSF implementation) – Using the Tree2 Component with JDeveloper 10.1.3 Implement JAAS based Authentication and Authorization for ADF Faces applications on OC4J 10.1.3 How to create a New Custom JSF Component that randomly displays select items in SelectOne… and SelectMany components Apache My Faces Trinidad: triggering Partial Page Refresh ("AJAX") from non Trinidad components 
JavaOne 2008: OpenSSO – creating federated relationships for secure SaaS, Social Networking and Web 2.0
