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.
As many of you will have noticed, recently we (the Seam team) have been putting our energy into other efforts than Seam 2. I've been working on Web Beans (the reference implementation of JSR-299). Shane has been working on the JSR-299 TCK (to test all implementations of JSR-299 for compatibility with the spec). Dan and I have spent a lot of time pushing some of the JSF improvements from Seam into JSF 2 (the proposed final draft should be up any day now!).
Adding to the stockpile of features that I've packed into seam-gen in recent months, I just committed a new seam-gen command that generates a front-end to Seam's identity management API (JBSEAM-3717). Identity management is one of the most significant additions to Seam in the Seam 2 code base. But since its just set of framework classes, you need something to tie it into your application to truly appreciate (or even give notice to) its potential.
I finally got around to weaving my modifications for adding GlassFish support to seam-gen (documented here and here) into the Seam project (JBSEAM-1619). While working on integration the changes, I managed to close the few remaining gaps and also add support for JBoss AS 5!
I'm pleased to announce the release of Web Beans 1.0.0.BETA1. This release implements around 90% of the JSR-299, Java Contexts and Dependency Injection specification. The only major feature missing from this release is support for annotating your beans using XML.
The revised Public Review Draft of Contexts and Dependency Injection (JSR-299, the spec formerly known as Web Beans) was approved by the EC with all EC members voting Yes, except for Nortel and SpringSource who did not vote.