The final release of RichFaces 4.3.1 (4.3.1.Final) has been released. This micro release addresses some bugs present in the 4.3.0.Final release, and offers some improvements on the new features introduced in that same release. Have a look at the 4.3.1.Final Release Notes for a complete listing if what was included in this release.

div(alert alert-info). To try out this release: You can download the distribution directly, or for maven users, increment the RichFaces version in your pom.xml to 4.3.1.Final. For more information on setting up a RichFaces 4 application, refer to our getting started guide.

Release Highlights

Perhaps the most significant change introduced in this release is in issue RF-12803, where we’ve included the <a4j:ajax> JavaScript service extension in <f:ajax> execution. This service allows RichFaces components to serve and execute JavaScript after the page content is loaded, leading to improved page performance. As we’ve continued to use this service more extensively throughout our components, we realized we had to integrate the extension with the JSF 2 <f:ajax> behaviour, or we would forever be reminding people to use <a4j:ajax> instead (which you should be using anyway for all sorts of additional reasons).

The RichFaces push component has been upgraded to use the latest release of the Atmosphere library, with the resolution of RF-12689. If you haven’t yet started using the easy-to-use RichFaces push component in your application (with optional CDI and JMS integration) be sure to follow these 4 simple steps for RichFaces Push.

Moving forward

With RichFaces 4.3.1 out, we will next shift gears back into RichFaces 5 development, working on the new consolidated RichFaces 5 repository. Stay tuned for a first RichFaces 5 milestone release!