"t.skultinas" wrote : I have missed the point how SFSB Business component
owning EM can control SLSB DAO which also contains EM. Or this EM from Business
SFSB should be passed to DAO SLSB?
The PC is propagated with the transaction context. As long as you hit the SFSB
first, and pick up the extended PC there, you will get the same PC in the SLSB.
"t.skultinas" wrote : 1) Different EM instances will be injected to different
DAOs what is not good if cascades in entities are not used (some design
solution can be found for this problem)
Not correct. Not as long as you propagate the TX.
"t.skultinas" wrote : 2) EM cache cleanup strategy because EM scope is session
and not conversation or request.
Also not correct. If the SFSB is conversation scope, then its extended PC will
be conversation scope.
"t.skultinas" wrote : I'm looking for some extended persistence context which
scope is less than session (like conversation) managing mechanism with
transaction and EM isolation support.
Right. An SFSB extended PC is exactly that.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946255#3946255
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946255
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
