Persistence Context propagation between Seam Components

breako Nov 23, 2007 12:58 PM

Hi,
Suppose I have two Seam components whic both use Seam Managed EntityManagers i.e. no EJB server.

In a request one Seam component uses the other. Is the persistence context associiated with the first EntityManager propagated to the second EntityManager in the second component?

What are the rules of persistence context propagation for Seam managed EntityManagers?

Thanks

1. Re: Persistence Context propagation between Seam Components

pmuir Nov 23, 2007 4:15 PM (in response to breako)

Assuming you are using Seam Managed Persistence Contexts, yes.
Actions
2. Re: Persistence Context propagation between Seam Components

breako Nov 26, 2007 6:02 AM (in response to breako)

"pete.muir@jboss.org" wrote:
Assuming you are using Seam Managed Persistence Contexts, yes.
Thanks for that. Is there ever any persistence context classing problems?

For example in the EJB world if a Stateless Session Bean makes a persistence context actively associated with the active transaction and then call out to a Stateful Session Bean, the Stateful Session Bean will try and make it's persistence context the active persistence context. Now because there already is persistence context, a clash occurs and hence some problems.

My question is if persistence contextx are propagated in Seam between Seam managed EntityManagers can similar problems manifest?
Actions
3. Re: Persistence Context propagation between Seam Components

pmuir Nov 26, 2007 6:07 AM (in response to breako)

No, its the same persistence context which is injected into each of the components in the current conversation.
Actions

Go to original post