The future of Seam 3

[hantsy]

I noticed there is a post

So what's happening with Seam?

The core of Seam 3 will be moved to the related dependent techniques?

It means the Seam team will stop to develop seam3 in future?

If seam faces is moved to richfaces, why not combine the effort of MyFaces, there is also a CDI integration?

[lightguard]

Keep watching for more information as we can make it available. Everything will work out. We're not going to be leaving our community high and dry.

[deverson]

I take this with a bit of hesitation - the Seam 2 community has been left high and dry already.  Why should we not expect the same for Seam 3.  For those of us who have embraced Seam since the start, deployed applications into production and then for the last couple years asking for JSF 2 support so that we can continue to build and enrich our applications with better component libraries such as PrimeFaces.  In the last several weeks several inquires AGAIN have been made on this subject.  As we have come to expect NOTHING.

We as an organization are seriously starting to look at frameworks such as Play! and even Spring is back on the table.

There is always this option as we start to question the need for Seam in a JEE6 world:
http://javalabor.blogspot.com/2011/08/our-seam-2-to-jee-6-replacement-list.html

[pgmjsd]

Dave Everson wrote on Sep 28, 2011 10:11:


I take this with a bit of hesitation - the Seam 2 community has been left high and dry already.  Why should we not expect the same for Seam 3.  For those of us who have embraced Seam since the start, deployed applications into production and then for the last couple years asking for JSF 2 support so that we can continue to build and enrich our applications with better component libraries such as PrimeFaces.  In the last several weeks several inquires AGAIN have been made on this subject.  As we have come to expect NOTHING.

Unless you're paying for support, complaining isn't going to get you very far.
How about contributing a patch to Seam 2 to provide JSF2 support?   The source code is freely available.  I'd probably use it if you made one.

We as an organization are seriously starting to look at frameworks such as Play! and even Spring is back on the table.

If you like some other framework, then use it.

There is always this option as we start to question the need for Seam in a JEE6 world:
http://javalabor.blogspot.com/2011/08/our-seam-2-to-jee-6-replacement-list.html

What's wrong with Seam being the main influence for CDI?   If you don't like the Seam 3 extensions then don't use them.   Totally disagree with the 'shooting themselves in the foot' comment re: Seam 2 and JEE 6.   Look at how Hibernate 3 influenced EJB3/JPA, same thing is happening with Seam 2 and JEE 6.   Open Source is about standards, not locking people in.

[deverson]

We did pay for support... $15K worth.  Support could not answer questions so they asked Gavin King.  Rarely did we get better support than asking in the forum.

[bitec]

Actually don't understand, why moving Seam modules to Jboss self projects makes the CDI ecosystem broaden. Moving Seam Faces to Richfaces means it will not work with Icefaces or Primefaces. Moving Seam Persistence to Hibernate project means it will not work with EclipseLink. Is this correct?

Seam was perfect as it was almost cross-platforms (different app servers, different JSR implementation, different web frameworks). Does this mean, that now some Seam modules will be bound only to specific Jboss projects?

Thanks.

[asookazian]

Dave Everson wrote on Sep 28, 2011 16:40:


We did pay for support... $15K worth.  Support could not answer questions so they asked Gavin King.  Rarely did we get better support than asking in the forum.

We used the JBoss support @ Cox (primarily for AS, Seam and RichFaces) and it was very helpful and they answered my questions typically within a couple days.  The support was typically more helpful and faster than this forum IMHO.