The RichFaces and Seam teams are nothing if not passionate about community, open source, and working with standard bodies like the Java Community Process (JCP). That is one of the reasons that Oracle/Sun's decision to disband the JSF expert group (JSR-314) with no successor JSR filed under which to develop future revisions of JSF is disappointing. Dan Allen summed up JBoss/Red Hat's position quite clearly in his letter to the JSR-314 public mailing list. While we want to continue supporting the JSF specification, not having an official JSF and EG, along with the intellectual property and governance guarantees this brings, makes this very difficult.

I want say something very clearly. I believe that the individual engineers are doing the best they can with their current priorities and constraints. They are still posting to the JSR-314 open mailing list, which you can view using the JBoss jsr-314-open-mirror), and asking for comments and patches. The RichFaces and Seam teams will also work within our current constraints and will work to resolve some of the core issues that will impact key features of JSF 2.0. While at the same time we will be pushing for a new JSR to be formed. Unfortunately, due to the above mentioned issues, JBoss's participation is limited, although we are fully prepared to contribute if the correct environment is present. When it isn't, we can only expect the spec leads to take on board our issues and push them.

As an example of the above, one of the major goals of the JSF specification is to enable component libraries to interoperate with each other within the same application, and ideally the same page. As component libraries develop to the new specification, and add features, we are finding areas where the specification needs to be updated. As there is no official JSR, and the specification priorities are driven by the RI priorities, some of these issues have been pushed to future versions of the specification ( with an unknown timeline ). Take for example #658 which deals with a problem with the PartialViewContext and how component libraries can extend it without breaking other component libraries. The RichFaces team has provided a draft patch to resolve this (thanks Nick) , however due to timing this will not be included in JSF 2.1.

With no known timeframe, JSR or expert group in place for JSF 2.2+ the Seam and RichFaces projects will continue to give our communities the features and functionality they expect, but in some cases this will need to be outside of the JSF specification. For example View Actions will be implemented by Seam Faces instead of being part of the specification for now. Richfaces has and will continue to reach out to other component libraries such as IceFaces, PrimeFaces, etc… to kick off discussions on how to address these issues outside of the specification. Hopefully we'll be able to deliver the interoperability that was promised, while prototyping updates for future versions of the specification.

Let's hope this situation can be resolved as soon as possible!

Back to top