[PJUG Javamail] Spring versus Seam

[Vijay Balakrishnan]

Hi Doug,
seam-gen creates a Service layer providing the level of indirection with
Bi-jection to boot using a Home, Entity and Persistence layer. I was worried
too initially about a Visual Basic type crap of accessing the database
directly.Basically, the UI layer interacts with the Home to get the Entity
using a home.getInstance() method.The Home also interacts with the
Persistence layer(could be JPA or Hibernate) to persist the data stored in
the entity.My apologies if this is a very short explanation.

As I said, Gavin King did design some very neat patterns into the Seam
framework.

BTW-I am not attached to JBoss or Seam in any form or shape but I have been
wanting a decent JSF framework that lets me focus on the Business problem
domain for a while.

Take a look at the design pattern they follow for it.


Vijay

On Mon, Oct 19, 2009 at 5:49 PM, Douglas Bullard <dbullard at nurflugel.com>wrote:

> One of the drawbacks with letting Seam do that is that you completely
> eliminate the concept of layering.  What happens when you want to switch
> from direct database access to using a service?  You no longer have a nice,
> neat data access layer you can switch out - your whole application needs to
> be tweaked.
>
> Doug
>
>
> On Oct 17, 2009, at 14:23, Vijay Balakrishnan wrote:
>
> 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
>>
>>
> _______________________________________________
> 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/20091019/dc318944/attachment.html