Hi Jacob!
If you can standardize on the EJB3 spec, then you can piggy back on
JBoss Seam for TX management and state management
I shy to use JBoss Seam in the "reference implementation". If you would
like to use JBoss Seam outside the JBoss Seam enabled JBoss Application
Server you have to add dozens of jars to your classpath, you know?
And I dont know if I really need all this management now. I dont see
this "conversational scope" now in Faces Freeway as any transaction will
be finished in the same view. Save/Edit/Delete will all happen on the
same page - and then I always can use Session.persist().
I am not an JBoss Seam expert so I dont know if it is easily possible to
plugin support for it later, but this might change in the future as I
would like to use JBoss Seam in our application too :-)
---
Mario
