PUBLIC MARKS from ddelangle with tag JSF

Conclusion: don't use JSF simply because it's a "standard". Use other frameworks that are more actively developed and designed for the web. For component-based frameworks, the most popular are Tapestry and Wicket. Less popular ones are RIFE and Click.

How to create a JSF component

Oracle is pleased to announce the donation of ADF Faces, a rich set of UI components based on the JavaServer Faces specification, to the Apache Software Foundation

I can see how JSF/ASP.NET + AJAX makes sense for small lookup type operations like auto completion and, of course, for encapsulating purely client side operations such as column reordering and simple validations. But if AJAX really catches on, what it ultimately means is that the whole request processing life cycle, on which these frameworks are based, is obsolete.

The article arose from having to make a recommendation on which of the two frameworks to use in a real project. It's a task I can imagine many Java developers facing in the months to come.