Now that RichFaces 3.3.3 is nearing its final release I wanted to take some time and discuss our plans for RichFaces and JSF 2.0 support in more detail.
The goal of JSF 2.0 support in the 3.3.3 release is to run your existing RichFaces 3.3.X applications in a JSF 2.0/EE6 environment with little or no changes. This is an important migration step for any large application, and infrastructure.
We have always meant the 3.3.3 release to be a stepping stone for JSF 2 support. We needed to make a trade off between retro-fitting 3.3.X completely for JSF 2.0 ( a major undertaking ), or have limited JSF 2.0 support in 3.3.X and push forward with RichFaces 4.0 where we can really get the most out of JSF 2.0. This is one of the reasons that we are working so hard to get RichFaces 4.0 out.
In addition to the information in our release announcements ( 3.3.3.BETA1 and 3.3.3.CR1 ) and our wiki page Richfaces 3.3.3 and JSF 2.0, a few people have also posted blogs and articles that I think explain the plans for RichFaces support of JSF 2.0 well. DZone posted RichFaces 3.3.3 Begins Support for JSF 2.0 and Max Katz has posted RichFaces 3.3.3 RC1 and JSF 2.
RichFaces 4.0 is where we can really innovate and extend features to get the most out of JSF 2.0. RichFaces did this for JSF 1.2 and we plan to push the specification to the limits, and prototype the future of JSF!
This is going to include:
- New Custom behaviors
- Dynamic resource extensions
- Simplified component development kit (CDK)
- Customizable request queues
- Updated skinning
- Consolidated component set ( with all functionality you expect )
- Performance tuning and review
- Semantic HTML markup changes to make styling easier
- Interoperability with other component libraries
- Module build system for easy contributions
Plus, all the flexibility and stability needed for large scale development. This does mean that taking advantage of some JSF 2.0 features with RichFaces will need to wait for 4.0. The good news is that we are well on our way to our next 4.0 release, and we will have several time-boxed milestone releases to jump start your development.
We are also going to have detailed migration instructions, scripts, examples and a migration bridge to assist users in moving their existing applications to RichFaces 4.0. The details of this are not completely worked out yet, but our goal is make it as easy as possible for users of 3.3.X to migration to 4.0.
I would like to encourage anyone with an opinion or an idea to contribute to the process. Take a look at our releases, post to our forums, check out our meetings and get involved!