In Relation To

Seam 2.1.1.CR2 is ready. We're really close to a final release, so please give it a test. Assuming we don't find any more issues, and right now things are looking good, you can probably look for a GA in the next week.

Seam 2.1.1 adds OpenID support as the first of, we hope, many external authentication options in Seam. Since this is fairly new, I've put together a mini-FAQ on our OpenID support.

DZone just published a Seam reference card, by Seam committer Jacob Orshalick.

I'm happy to say that Seam 2.1.1 is one step closer to being done. We've just released Seam 2.1.1.CR1, so please take a look and let us know what you think. CR1 is largely a bug-fix release, with a number of notable performance improvements, especially around hot deploy. We've added support for PDF forms to the iText integration, and there's preliminary support for OpenID, but you'll have to wait for CR2 for the example and docs. Seam-gen now generates IntelliJ IDEA projects. And, I should also point out that we've changed a few of the URLs on examples to match up better with the example names.

Devoxx, the show formerly known as JavaPolis is coming up soon and while I was preparing for my talks I started browsing the full program and saw it is going to be great for anyone interested in Hibernate, Seam, JBoss Tools, JBoss AS and other JBoss technologies.

I keep getting asked about the relationship between Seam and Web Beans. At a high level, the mission of the Seam project remains unchanged: to provide a fully integrated development platform for building rich Internet applications, based upon the Java EE environment. In Seam2, this platform consists of the following layers:

It's fun to see what people are using Seam for:

IntelliJ IDEA 8 has Seam support. Cool!

The 2.1.0.SP1 release of Seam contained many features and updates, one of which is an updated Weblogic integration reference guide chapter

The Seam 2.1.0.SP1 release included a new reference guide chapter describing Seam integration with GlassFish v2. As with most container integration the bulk of the work is reconciling library differences, datasources and deployment descriptor changes. Glassfish is no different in that regard, however it is much easier to integrate and work with GlassFish than some of the other containers that I written about.