is one of the leads on the web beans
spec. So we might get JSR-299 support for free because we integrate
with Guice. (At least that was my hope) That's why I haven't done
much more with it. (That and a lot of the spec isn't applicable to an
action based framework)
Tom
Ted Husted wrote
2007/12/17, Brian Pontarelli [EMAIL PROTECTED]:
One thing I noticed that I thought might be a good idea for session
safety was to move the flash Map from the session to the request on the
first usage of that scope. That way the flash is not there any longer,
in case of failures.
That it
Hello,
I' just looked at jBoss Seam documentation. I wonder if anyone allready
suggested to have similar features on Struts actions, that seems not so
difficult to implement, by mixing an OpenSessionInView interceptor, some
ModelDriven elements and injecting a JPA EntityManager in the action.
As
I think Ted and I started a conversation briefly about this, and I
know there was a thread on openjpa-users a while back. The
OpenSessionInView doesn't really translate well to JPA and
EntityManagers. In Hibernate, you have a 'getCurrentTransaction' (or
is it getRunningTransaction, I can't
This is one of the founding principles that we put into JCatapult. It
uses Guice, which is pretty good for DI and Hibernate for JPA. JCatapult
uses a Filter to implement open session in view using Guice and it works
well. An interceptor could work for Struts only applications as well.
but with JPA, there is a one-to-one relationship with EntityManagers and
transactions.
Not true if you are speaking about extended persistence contexts. Also, even
transaction-scoped EntityManagers don't require a transaction for read only
queries.
If by alternate implementation, you mean an implementation of JSR
299, that's something best discussed with the MyFaces group.
Evidentially, Shale is merging with MyFaces, making MyFaces our
one-stop JSF shop. :)
Meanwhile, Don's been working on a scope plugin in the sandbox that
mimic's
understanding is that Bob Lee is one of the leads on the web beans
spec. So we might get JSR-299 support for free because we integrate
with Guice. (At least that was my hope) That's why I haven't done much
more with it. (That and a lot of the spec isn't applicable to an action
based framework
