My recommendation is to have a read through the specs and then go with Seam 2 but staying clear of stuff that you didn't see in the specs (as such features might have a harder migration path). Examples might be outjection, named entity beans etc... If your used features are mostly compatible you might get away with a renaming of the annotations and some minor tunings to have a
I understand there is a
compatibility layerupcoming but why drag in legacy stuff if you can avoid it when starting fresh...
Thanks Nicklas for your inputs !
The other big thing to consider is that as far as I am aware there is no release schedule for seam 3, and I can't really see work begining on it until after web beans goes GA. I am only guessing here, but I don't think we will see seam 3 go GA before the end of 09.
Indeed...this is the most important topic in our project at the moment
we are planning to complete one small project using Seam2.1.x and major business enterprise project can be started with Seam3 with some delay
Thanks for your suggestion Stuart :)
that's a great news for Seam lovers :)
It was worth waiting for 2 months. Have a look
Expecting final release in August, in time for the Java EE 6 release in September :)
great news for JEE world !