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

Wed May 30 14:02:08 EDT 2007

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

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

Sounds good.

>but IMO that is not something we really need to support at this point. 

I agree, however, I'm not saying that Seam should provide support for these types of edge cases but should just try not to get in the way if an application decides it needs to do something out of the norm.  I think Seam's component model does a good job of facilitating this type customization where necessary approach.  So, question is not what should Seam support but rather where should Seam draw the line.

> 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.BETA1
>
>
> 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