Seam long-running nested transaction isolation with jpa and extended managed persistence

[ricardo.bento]

I have one long running conversation and would like to persist or update in a nested conversation another object without firing eventual changes made to other objects and prevent commits or updates in parent conversation.

Anyone has already had this issue and had a resolution?

Thanks in advance.

Ricardo B

[vata2999]

Are you using @PerNestedConversation?

Limit the scope of a CONVERSATION-scoped component to just the parent conversation in which it was instantiated. The component instance will not be visible to nested child conversations, which will get their own instance. Warning: this is ill-defined, since it implies that a component will be visible for some part of a request cycle, and invisible after that. It is not recommended that applications use this feature!