Since the Red Hat shutdown just began, don't interpret silence on this
thread as no response. You'll likely get some responses come Jan 4th.
I'll give some responses as I see it, but expect more replies/clarification
in due time.
On Wed, Dec 23, 2009 at 8:28 AM, Denis Forveille
It seems that everybody get very excited about the development of
v3 and that's cool.
We are getting excited primarily to get some momentum behind Seam 3. In
January things are really going to pick up. But it's a ways until we can
really have something that comes near as complete as Seam 2 (meaning
security, jbpm, drools, JSF, etc).
But what about the development of Seam v2?
Is there a planned released date of Seam v2.2.1? (There are
1000+ JIRA entries for Seam v2, 100+ assigned to Seam v2.2.1)
Will we have a Seam v2.2.2 (or maybe v2.3) in the future?
We did discuss this in the Seam meeting last week. We are very likely going
to be getting a release out in early 2010 (I don't know the estimated date)
for reasons you cited and because we'll need changes anyway for the Seam 3 -
Seam 2 bridging effort.
Also for seam v2.0.3 which is in CR since months, should it be
possible to either release this version or cancel it?
I'm not sure. Stay tuned for a response on that.
As discussed in the weld forum, us, users of seam v2/EJB 3.0 but poor
non glassfish v3 (or JBoss v6) users will have to wait for months
before we'll be able to use weld and seam v3 in production.
The question is what are the plans to maintain seam v2.2 until 1) seam
3 is GA and 2) WebSphere/Oracle/WebLogic/<name your production AS
here> offer a JEE6 compliant version of their AS?
We understand that Java EE 6 is very cutting edge and migration to it will
take time. As Gavin said on in.relation.to, if you already have a project in
place or you need to deploy in the next couple months, Seam 2 is still a
very solid choice. If you are looking further out, perhaps prototyping some
projects, then EE 6 is definitely where you should be looking. (But you are
going to have to mind the dust if you are tapping into Seam 3 modules, since
they are in the early stages).
All our development is based now on Seam v2 (and I hope many other
users in the world..) and we are very happy with it but I think a
clear statement should be made on the strategy for Seam v2.x in the
meantime for the current Seam users. Or maybe it is somewhere and i
Basically, don't confuse our excitement with abandonment. I think what you
are looking for is some assurance for Seam 2 that haven't been clearly
stated yet. It is our intention (from my understanding) that you will be
able to continue to run Seam 2 applications on JBoss 6 (mixing Java EE, CDI,
etc), which translates into bug fix releases. I think what you probably
won't see in Seam 2 is new features (unless they are driven primarily by the
Personally I will continue to commit bug fixes when I see the fit
this in Seam v2.x but what about the rest of you guys? At some point
I'll for sure try to participate to the Seam v3/Seam v2 integration
module when the time will come to migrate our apps (And WebSphere will
provide an implementation of CDI).
It's important that you come forward with these requests. Obviously, we want
to make sure we are headed in the right direction, at the right pace to suit
the needs of the users.
I'll ask again that you be patient for responses until after the holiday ;)
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597