Originally posted by rob tirserio: I've read that Seam uses (and improves upon) the JSF lifecycle. How does it do this and what are some of the most significant improvements that Seam makes to the JSF lifecycle?
You'll be happy to know that the entire chapter 3 covers this very question. All 50 pages.
The two most important features that Seam adds to JSF are a front-controller and global transactions.
The first let's you execute actions when a page is requested just like Struts. It then has a really fancy declarative navigation facility to let you redirect the user afterwards, and after any JSF action (say goodbye to faces-config.xml).
The second is critical in that no other framework wraps a web request in a transaction. You can feel totally safe in Seam to execute database operations in the view and not have to worry about isolation concerns.
Finally, I will mention that Seam adds an exception handling facility to JSF, which is probably the worst omission in JSF in terms of "how the hell did they miss this one?"