[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-1365) Make SeamManagedEntityManagerFactory joinTransaction if available

[Michael Youngstrom (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1365?page=all ]

Michael Youngstrom resolved JBSEAM-1365.
----------------------------------------

    Fix Version/s: 1.3.0.ALPHA
                       (was: 1.3.0.BETA1)
       Resolution: Done

The fix applied to JBSEAM-1144 has solved this problem as well.  If your project is not using JNDI to obtain a JTA transaction then you can extend org.jboss.seam.transaction.Transaction and Seam will call joinTransaction if a transaction is active.

> Make SeamManagedEntityManagerFactory joinTransaction if available
> -----------------------------------------------------------------
>
>                 Key: JBSEAM-1365
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1365
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Spring
>    Affects Versions: 1.2.1.GA
>            Reporter: Michael Youngstrom
>         Assigned To: Michael Youngstrom
>             Fix For: 1.3.0.ALPHA
>
>
> Spring correctly assumes that if EMF.createEntityManager is called while in a transaction that the newly created EntityManager will be joined in with the current transaction.  However, in the Seam Spring Integration, when Spring calls EMF.createEntityManager we might return an existing conversation scoped EM instead of a newly created one.  In which case we need to join the current transaction if there is one since spring will not.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira