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!).

But we've still found some time to work on Seam 2. We've closed over 110 issues since 2.1.1, so it's definitely time for a new release. We plan to release Seam 2.1.2.CR1 the week starting 13th April, and 2.1.2 the week starting 27th April. The focus of this release is bug fixing.

Those of you who work with jBPM and Drools will be pleased to know that we will fully support jBPM 4 and Drools 5 in the 2.2 series. As we want to get 2.2.0 out before the jBPM 4.0.0 release, we're going to make the jBPM integration pluggable, so that you can simply drop the jBPM 3 integration in favour of jBPM4, when it is released. We plan to release 2.2.0 in mid June.

At the same time, we'll be pushing ahead with Seam 3, so expect an alpha in the next few months. And never fear, we will provide a migration path from Seam 2, to Seam 3 :-)

02. Apr 2009, 22:49 CET | Link

Great job! Great updating!

03. Apr 2009, 01:22 CET | Link
Rory Sandoval | rorysandoval(AT)

Super good!.

Is Seam 3, more like WebBeans?... can you give us some advances?.

03. Apr 2009, 02:34 CET | Link
bbb | bb(AT)

I love Seam :)

03. Apr 2009, 04:02 CET | Link
Demetrio Filocamo | filocamo(AT)

Hi, I would like you (the team) to keep in consideration topics like this:

I think it's very important to give a final answer about Seam (2.x and WebBeans/Seam 3.x) optimization, the future of Seam 2.x (I think you gave something in this post) and how simple (or hard) would be to port Seam 2 apps to WebBeans/Seam 3.

Thank you and very good work on everything!!!


03. Apr 2009, 07:38 CET | Link

There have been some efforts on this so far (e.g. scalability work from Jay, Dan has a series of blog posts). This could definitely do with more love though - and is a great area for the community to get involved - not least as you are the ones with the large apps that show these problems, and have also worked out the ways around common problems. So, write up your approaches to solving performance issues and link them here; do scalability analysis, find out where the bottlenecks are in Seam (or JSF or...), and open a JIRA, attaching a way to reproduce, and someone can take a look.

Initial results for Web Beans performance look good - but this is just based on my feeling of responsivity of test apps...

If members of the community are interested in maintaining the 2.x branches, that would be great. The usual rules apply - provide patches, with test cases, for bugs in JIRA that show you understand the code base. Submit enough, and you will be noticed :-)

Migration from Seam 2 to Seam 3/Web Beans

I can say for sure that there will be a bridge (like the Seam/Spring bridge in Seam today) for accessing Seam components from Web Beans and vice versa. We should have a first iteration of this for the next Web Beans release. This will be great if you have a component library in Seam that you want to reuse in a Web Beans app.

Running your Seam app natively on Web Beans is another matter. I have some ideas about how to do this - but they are just that, ideas, so I need to develop them more before talking about them. And of course, the more time we spend on this, the less time there is to work on new features (such as porting existing Seam stuff like Mail etc.) which impacts on the schedule.

My current thoughts (which I still need to formalize and discuss with everyone, so this isn't written in stone) is that we could support 95% of the Seam annotations and perhaps 40-60% of the Seam programmatic API natively. The key here is to make sure we support the most common APIs, so that your changes to new APIs are small. I plan to put up a poll soon to see what APIs are most common

03. Apr 2009, 16:00 CET | Link
I really really really hope optimization is considered in Web Beans. Also it would be nice if the seam bridge would be optional so that you could keep Web Beans more lightweight.
04. Apr 2009, 00:59 CET | Link
Demetrio Filocamo | filocamo(AT)

Hi! Thank you very much for your answer, very soon (in some months) the optimization phase will start for me and I will be happy to study this field and try to find something (how other ppl are doing also now), the important thing is that you keep an eye on that because it's very important for a lot of ppl out there.

The last question: I've found a lot of post telling that javassist is very slow, but in general you can't find a final word on this, can someone that analyzed the problem explain this better (if it is or it's not)...

thanks for the great work on Seam and WebBeans!


04. Apr 2009, 05:12 CET | Link

My experience of javassist is exactly the opposite - it is very fast.

09. Apr 2009, 22:25 CET | Link

Great but Wicket is going to work (seamless) in this version?, or we do have to wait next version?

10. Apr 2009, 01:05 CET | Link

Wicket support is pretty good in 2.1.1 (if you've got a specific feature request add it to JIRA - but Clint has done a great job of fleshing out the support - 2.1.2 contains a maven plugin and ant task for instrumentation, lots of bug fixes, improvements to supporting both JSF and Wicket and more...

30. Apr 2010, 16:48 CET | Link
K Himaanshu Meehirs' Shukla | acmehimanshu(AT)
Hi All,

I am new in SEAM. Can anybody pls send me the links from which I can learn Seam in simpler way. My email id is : ‘’.

Thanks in advance...
-K Himaanshu….