  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Subject: - Re: Warning: do not use Seam managed pesistent context for B | Subject: - Re: Warning: do not use Seam managed pesistent context for B 2007-10-01 - By koenhandekyn
Back The good news is that indeed, a joinTransaction() call does the job with @(protected) injected entityManager.
anonymous wrote : Of course the @(protected) EM will not join the transaction automatically because the transaction is started AFTER injection, when the method is called
i think i understand your remark: seam injection occurs just in front of each method invocation and the transasction is only started in the method!
however, @(protected) injection occurs somewhere at bean creation and even earlier if i understand well.
so while I think I understand the seam behaviour now (joining makes sense), i 'm still confused why i don't have to do a joinTransaction with @(protected) injected entityManager (where does the join happen?) and why the behaviour should be different.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic &p=4090276#4090276
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode =reply&p=4090276 __ ____ ____ ____ ____ ____ ____ ____ ____ ____ jboss-user mailing list jboss-user@(protected) https://lists.jboss.org/mailman/listinfo/jboss-user
|
|
 |