2009/2/6 David Blevins :
>
> I guess my first question would be is this in use in a test case or in
> another environment like Tomcat? If in a test case, how do the setup and
> tear down's work? I.e. are OpenEJB and Seam being torn down together and
> are they being torn down before and after eac
Hi Guys,
Not entirely sure on the Seam angle, but in terms of
javax.ejb.PersistenceContextType.EXTENDED the persistence context
automatically propagates from the SFSB that created it to any SFSBs
that that bean created either via injection or JNDI lookup.
Here's a test case which illustra
Hi Thomas,
All my SFSB are also Seam components and live in conversation context.
So the extended persistence context is kept in a Seam conversation.
For what I understood, if you don't use Seam you have to propagate the
persistence context yourself.
You can read this in Seam documentation :
"Se
Hi Olivier,
I´m currently struggling with using the Extended PersistenceContext in multiple
SFSB.
Can you tell me, if it is working for you and what you did to make it work.
As soon as I try to inject the same EntityManager into another SessionBean I
get the following error:
DEBUG - finished in
On Jan 20, 2009, at 2:54 AM, Olivier THIERRY wrote:
Hi,
I use Open EJB to run TestNG unit tests in a Maven project. This
project contains many Seam components. All of them are EJB3 stateful
session beans (conversation scoped) and use extended persistence
context (same persistence unit everywhe
Hi,
I use Open EJB to run TestNG unit tests in a Maven project. This
project contains many Seam components. All of them are EJB3 stateful
session beans (conversation scoped) and use extended persistence
context (same persistence unit everywhere). All of these Seam
components work perfect ... excep
