Red Hat
Oct 21, 2008
by Pete Muir

As you've probably noticed, we've been busy over the last month preparing the Seam 2.1.0 release - and I'm pleased to say that it's here! Some of the highlights from Seam 2.1.0 include an identity management, ACL style permissions, an Excel reporting module, a revamped seam-gen, first class support for Wicket, built in support for URL rewriting and a technology preview of JAX-RS support through Bill Burke's RESTeasy project.

We've also made numerous improvements to Seam Core to make your life with Seam easier - better support for send mail from an asynchronous method, support for JBoss Cache 2 and EHCache as well as JBoss Cache, faster SeamTest, better support for concurrent requests to conversations. We've also kept track with JBoss 5, increasing the number of examples that work; of course, you can deploy your Seam appliction to most major containers - WebLogic, WebSphere, OC4J and Glassfish all have comprehensive documentation. Seam integrates with a huge number of other libraries and frameworks, and Seam 2.1.0 updates these to their latest versions, such as RichFaces 3.2 and Groovy 1.5.

JBoss has always been committed to open standards - bringing our experience with Hibernate to JPA and a strong showing in many JCP (and other) standards bodies. And that is why we took many of the ideas and concepts in Seam and sought to standarize them by leading the Web Beans specification. Speaking of which, work on the Web Beans RI has started, and the public draft should be published soon...

Next up, Seam 2.1.1! We'll be focusing on performance, scalability and clustering; Jay and Shane have already made a great start on scalability analysis, which has resulted in a 12-17% increase in performance under load. Watch this space for more! Marek and Dan will be working closely with the JBoss Clustering team; their aim is two-fold, to increase your understanding of how to use Seam in a cluster through documentation and examples, and to improve entity-replication. I think Norman is planning to slip OpenID support in :-) We should have a pretty quick turnaround for this release too!

Original Post