RichFaces 3.3.1.CR1 has been uploaded to the JBoss repository. We are on track for the early May GA release. Then we are on to RichFaces 4.0 more to come shortly.
On Thursday, April 9th I will be presenting an introduction and preview of Java Server Faces 2.0 at the New England Java Users Group (NEJUG). The talk will be given at Sun's Burlington Massachusetts campus.
RichFaces 3.3.1.BETA3 has been uploaded to the JBoss repository. We are getting close to the release and continue to stabilize the code base on the way to final release.
The anticipated conclusion to my two part article on how to improve the performance of your JSF-based Seam application by two orders of magnitude is finally available at JSFCentral. I've also released the source code cited in the article.
RichFaces 3.3.1.BETA2 has been uploaded to the JBoss repository. We continue to stabilize the code base on the way to final release.
RichFaces 3.3.1.BETA1 has been deployed to: jboss repository and ready for community preview.
After an alpha, a beta, 2 CR's and countless nightly builds I'm proud to present the JBoss Tools 3 release!
The first part of my new article, published today on JSFCentral, explains how you can increase the rendering performance of a data-driven, JSF-based Seam application by two orders of magnitude! The article originated out of a contract job I did over the summer (before joining Red Hat). I worked for a group of scientists to develop a data-driven application using Seam, JSF, and RichFaces. That means it comes straight to you from the real-world ;)
In the previous article we spoke about annoying issue of the Mojarra 2.0.0 PR when the empty attributes are rendered to the final html code. The issue was posted to the Mojarra project: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=940
Every JSF component has some specific attribute set unique for it. At the same time, almost all UI components have attributes that are common for all of them. For example, onclick, ondblclick, onblur, onmouseover, onmouseout, onmousedown and so on. They are named PassThru because they are rendered one-to-one to the final html layout.