[EMAIL PROTECTED] wrote : The scope is conversation. The same Persistence
Context will injected by @In (or via programmatic lookup) during the lifetime
of that conversation. If you inject via @PersistenceContext, it isn't a SMPC.
Thanks for that.
Just to confirm, there is no way to propagate a
Not afaik.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4116688#4116688
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4116688
___
jboss-user mailing list
breako wrote : Hi,
| If Seam managed EntityManagers are being used, the Persistence Context
propagates between the EntityManagers that are in the same conversation. This
is very good and useful.
|
| I am just wondering if another component, for example an EJB is using an
EntityManager
The scope is conversation. The same Persistence Context will injected by @In
(or via programmatic lookup) during the lifetime of that conversation. If you
inject via @PersistenceContext, it isn't a SMPC.
View the original post :
If you say what it isn't, also say what it is:
### Eclipse Workspace Patch 1.0
| #P jboss-seam
| Index: doc/reference/en/modules/conversations.xml
| ===
| RCS file:
A question then is:
What's the different behavior then with the back-button in the browser,
different for propagation none versus end.
Seam supposedly (and as far as I have seen) is quite gracious about using the
browser back button and then continuing to work from there.
But isn't that
Much of the last question is answered in Seam reference 7.1.2. Seam and the
back button.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4028557#4028557
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4028557
codelion wrote : That implies currently there isn't a simple way to end
all nested conversations without keeping them around, i.e. not at the level
above Java coding. Or is there?
Is this related to the feature request
http://jira.jboss.com/jira/browse/JBSEAM-566 ?
I'd like the ability to
End causes the conversation to be demoted to a temporary conversation (which
then ends at the end of the current request). None causes the conversation not
to be propagated - if you looked at the conversation list on debug.xhtml or
displayed a list of conversations to the user it would still
That implies currently there isn't a simple way to end all nested
conversations without keeping them around, i.e. not at the level above Java
coding. Or is there?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012388#4012388
Reply to the post :
10 matches
Mail list logo
