[jboss-jira] [JBoss JIRA] (WFLY-441) If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene updated WFLY-441:
------------------------------

    Fix Version/s: 8.0.0.Beta1
                       (was: 8.0.0.Alpha3)

    
> If possible, eliminate the NonTxEmCloser by closing the EM immediately after each EM invocation
> -----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-441
>                 URL: https://issues.jboss.org/browse/WFLY-441
>             Project: WildFly
>          Issue Type: Task
>          Components: JPA / Hibernate
>            Reporter: Scott Marlow
>            Priority: Minor
>             Fix For: 8.0.0.Beta1
>
>
> For Queries, handoff the EntityManager to a Query object wrapper and have the Query object finalizer close the EntityManager.  
> Make sure that we respect JPA 2.0 section 3.8.6 (detach objects returned from Query object).
> 1.  Methods that return a Query, will hand off the EM to the Query object wrapper.
> 2.  Other methods will close the EM at the end of the EM method invocation.
> When making this change, make sure that performance doesn't degrade.  The cost of this change, will be that each (transaction scoped non-tx) EM invocation will create a new persistence context, but we can eliminate the NonTxEmCloser which has its own overhead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira