I think probably Hivemind/Tapestry can do it if we strengthen its
session model. For example, including "conversation-scoped" ASOs,
another way of building ASOs rather than the StateObjectFactory, etc.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Ivano wrote:
AFAIK Seam's mission is to "fill the gap" between the EJB3 container
persistence layer and the JSF presentation layer.
The idea is that both EJB's entities and JSF's model objects are
beans, so why should one want to write session-beans to link those
objects.
Seam should be this "linker" that ties up the JSF View directly with
persistent beans. It also introduces new conversation scopes for the
lifecylce of those beans.
So my opinion here is that trying to use Seam without JSF could be
done but it would be kind of twisting the original idea behind the
framework.
Maybe Spring Webflow could be a better choice?
Ivano Pagano.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
