Mitch Pronschinske is a Senior Content Analyst at DZone. That means he writes and searches for the finest developer content in the land so that you don't have to. He often eats peanut butter and bananas, likes to make his own ringtones, enjoys card and board games, and is married to an underwear model. Mitch is a DZone Zone Leader and has posted 2574 posts at DZone. You can read more from them at their website. View Full User Profile

RichFaces 3.3.3 Begins Support for JSF 2.0

  • submit to reddit
The JBoss component library for Java Server Faces, RichFaces, is swiftly approaching a final release for version 3.3.3 with the availability of CR1.  The primary new feature of this release is the beginning of support for the JSF 2.0 spec, which is part of the Java EE 6 web tier.  The focus of this release is to allow developers a chance to try using JSF 2.0 while still maintaining the innovative support for JSF 1.2.  Full support for JSF 2.0 will arrive in RichFaces 4.0, which is currently in alpha.

Facelets is the new official view technology for JSF 2.0, eliminating the need for workarounds for well-known life-cycle conflicts with Java Server Pages.  Component and tag creation with Facelets will also make life easier for developers by using XML markup instead of Java code.  Page transitions in JSF 2.0 are invoked by passing the name of the desired View/Facelet.  RichFaces 3.3.3 does not support built-in Facelets (VDL), but Facelets can be used.  Facelets 1.1.15 should still be used because of RichFaces' dependencies from the Tag Handlers classes.  JSF 2.0 will also give RichFaces users access to Java 5 annotations such as @ManagedBean and @ManagedProperty, which removes the need for faces-config.xml in all cases except for framework extension.  

Partial State Saving and DOM updates are part of the built-in Ajax support for JSF 2.0.  There is also built-in support for handling resources such as images, CSS, and Javascript.  Artifacts can be included with component libraries, separated into JAR files, or co-located into a consistent place within the web-application.  JSF 2.0 also includes logical naming and versioning of resources, support for events, RAILS_ENV-style development stages, and an expanded standard set of components.

RichFaces 3.3.3 will let you run your applications with JSF 2.0 and start preparing them for the eventual full switch to the new spec.  RichFaces 4.0 will feature complete JSF 2.0 integration, development, and extensions.  It will include Ajax framework improvements that extend the JSF 2 spec and a simplified development kit with annotations, advanced templates, faces-config extensions, and more.  Along with server and client-side performance enhancements, RichFaces 4.0 will also feature a redesigned modular repository and build system.


Cloves Almeida replied on Thu, 2010/02/18 - 4:59pm

What richfaces guys do is close to a miracle given the mess that JSF is. At least JSF 2.0 will makes things more usable.


Fab Mars replied on Fri, 2010/02/19 - 4:00am instead:

What RichFaces guys do is stunning and is a perfect use case of the extension points JSF provides.

Oleg Varaksin replied on Fri, 2010/02/19 - 4:56am

"Begins support for JSF 2" ? Guys, you are too late. JSF 2 was out many months ago. PrimeFaces already offers JSF 2 support and wins new customers. How long can we wait yet for fully JSF 2 support?

Jay Balunas replied on Fri, 2010/02/26 - 10:56am

First this was a great article thanks!

Second I just posted a blog laying out RichFaces roadmap for JSF 2 support.  You can check it out here :


Gauthier Willia... replied on Thu, 2011/07/07 - 4:17am

The article is really informative for me because it really tackles the RichFaces and JSF2 support. The two will be a great combination. If the article is true then we will be having a great JSF2 if the 4.0 version of RichFace will be release. Senior Healthcare Consultants

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.