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

Tue May 29 21:25:18 EDT 2007

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

Michael Youngstrom commented on JBSEAM-1365:
--------------------------------------------

You're right, it does as long as you're using Seam managed transactions.

I figured it wouldn't hurt to have the spring integration do it as well in case the user is not using Seam managed transactions.

If you would prefer for something like this to wait until Seam Managed Transactions really are optional then I would understand.

Though it doesn't hurt anything and comes in handy for me in 1.3.0Alpha since I've found an ugly hack to get around JBSEAM-1363 for my particular project.  And might come in handy for anyone else who finds a way around JBSEAM-1363 before 1.3.0Beta.

Let me know.

Mike

> 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