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.
Andrew Pym wrote:
Am I right in that JBoss has come up with a product which is very HiveMind like
in Seam?
http://docs.jboss.com/seam/reference/en/html/pr01.html
The documentation puts Seam at the Context Management layer,
Above EJB & Hibernate but below JSF and Presentation layers,
although also described as a uniform component model which hooks into jBPM
Am I right in saying that HiveMind does context Management plus a bit more and
has a bit more flexibility than Seam?
Does anyone have any suggestions for hooking Hivemind & Tapestry up to a
workflow engine eg OSWorkflow or jBPM?
Regards
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
