[PJUG Javamail] Spring versus Seam

[Chris Kessel/Lou Doherty]

We used it about 9 months ago on a project where I worked and Seam was nice
in concept, but just chocked full of bugs. All sorts of problems with
iterators on persistent items and such, especially as related to Seam GUI
components. We spent a lot of time working around bugs and/or trying to
figure out if if something was us or the Seam library with the probelm. We
even had a couple, um, Red Hat(?, whoever bought JBoss) consultants helping
us work around the issues and it was still painful. Seam was pretty heavily
tied to Eclipse only too, so if you're not an Eclipse-only shop, you might
have cross IDE issues.

 

9 months ago though is a lifetime in the maturity of an early product, so
take my comments with a grain of salt for how it might be today. Personally,
I like Spring and would probably use that and it's JPA integration with some
other GUI entirely (like GWT, Tapestry, etc).

 

Chris

 

From: javamail-bounces at pjug.org [mailto:javamail-bounces at pjug.org] On Behalf
Of Vijay Balakrishnan
Sent: Saturday, October 17, 2009 2:23 PM
To: Bruce Kaufman
Cc: javamail at pjug.org
Subject: Re: [PJUG Javamail] Spring versus Seam

 

I have looked at Seam and it is definitely a very elegant, tightly
integrated solution for a stateful web app trying to access a hibernate or
JPA based app on JDK5. Seam also takes care of the back button issue like
Spring MVC. It also integrates ICEFaces and RichFaces in and also has jBPM
support with Drools(I think). Seam takes care of the LazyInitialization
issue that happens commonly with Spring apps talking to Hibernate(source of
a long email chain on PJUG recently). That is 1 of the main reason Gavin
King, the Hibernate guy went for the jugular in his dispute with Spring
which is a stateless framework. Seam also plays well with Spring framework
if you insist on it.Spring is trying to get back at Seam with Spring Roo but
it is still in beta and a newly started project.

 

Seam fixes a lot of the issues with JSF1.2 and handles all the scenarios you
have mentioned below.

"Seam In Action" is a great starter book.

 

If you have a backend database schema you can point to, seam-gen Ant task
will generate all the CRUD code all the way to a working Web UI using JSF
and Facelets(it uses HibernateTools for the reverse engineering and
Hibernate templates to generate the UI/View layer).

 

Vijay

On Sat, Oct 17, 2009 at 9:23 AM, Bruce Kaufman <bjan11 at gmail.com> wrote:

I am looking to refactoring my web application (currently RichFaces) to use
either Spring or Seam. I am looking for a more elegant solution for
"stateful" situations and the "browser back" key.

Has anyone recently evaluated them and have any comments?

Thanks,
Bruce Kaufman
www.WoodsWithNoBorders.com



_______________________________________________
Web Site - http://www.pjug.org/
Javamail mailing list
Javamail at pjug.org
http://www.pjug.org/mailman/listinfo/javamail

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pjug.org/pipermail/javamail/attachments/20091017/002ac2f1/attachment.html