This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I havent used JSF before, nor have i tried my hands at SEAM yet. As per Gavin, one of the reasons (or i guess the primary reason) why SEAM was started was :
Seam was born out of our frustration with the limitations of todays stateless application architectures (stateless session facade, Spring, RoR, etc), which do not include constructs for modeling optimistic transactions, and therefore cause all kinds of problems for Hibernate users (LazyInitializationException and his friends).
My question is why was JSF singled out or rather chosen for SEAM? The LazyInitializationException and the stateless architecture was common in other application too (for example application using Struts). [ June 05, 2007: Message edited by: Jaikiran Pai ]
When starting Seam, we actually looked around at the various web frameworks. JSF was ultimately chosen because:
It is a standard. It has an extremely powerful and flexible request/response model that provides what we need for complex features like conversations and intelligently-managed persistence/tx It supports a component-based development model. Not only is it simpler and more powerful than action-based frameworks, it has a lot of potential for tooling.
However, Seam really doesn't have to use JSF. It's entirely possible for someone to decide they would rather use a different web framework and to write the integration bits for that framework. I don't foresee that happening because JSF turns out to work really well in practice, at least in the context of Seam where we have already taken the rough edges out.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com