Before I start, I want to mention that Seam 3 is extremely green right now. The main motivation for jumping into now is to work out the kinks in the JSR-299 and JSF 2 implementations. Plus, I'm starting to get the word out about what's going on with Seam 3 so that you can help drive its future and be a part of the process.
JSR-314 has passed its final approval ballot. Finally, JSF gets a chance to live up to its promise. JSF 2.0 brings a bunch of innovation that happened in third-party extensions (including Facelets, Seam and Ajax4JSF) back into the specification. Back in July '07, I wrote up this wishlist and it's great to see that most of the issues on this list (and much more) have been addressed. It takes an enormous amount of work to put together a specification like this, so please join me in thanking the expert group. Of course, I should especially thank the members of my team (Dan Allen and Pete Muir) who worked hard on getting some important features in very late in the cycle.
Good news! We've just gone live with Seam 2.1.2.CR2. This release puts us right on the brink of a final release, with only documentation issues and a little more testing remaining on the work list. If you haven't already done so, now is the time to test the release with your Seam projects and report back issues, as the next scheduled stop on the Seam roadmap will be Seam 2.2.
Last week I recorded a couple of podcasts. The first one, with Nitin from DZone, gives a good overview of where we are going with Web Beans and Seam 3 - we talk about what JCDI is, how it fits into Seam 3, and the migration path.
We've been busy with the JSR-299 specification (Contexts and Dependency Injection for Java EE) over the last couple of weeks, preparing to submit a Proposed Final Draft in early June. At this point I would like to solicit feedback from the community on the recent changes, so I'm posting a current revision of the specification here.