[jira] Updated: (OPENJPA-159) Make ManagedRuntime amenable to more transaction execution strategies

["Kevin Sutter (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENJPA-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Sutter updated OPENJPA-159:
---------------------------------

    Issue Type: Sub-task  (was: Improvement)
        Parent: OPENJPA-61

> Make ManagedRuntime amenable to more transaction execution strategies
> ---------------------------------------------------------------------
>
>                 Key: OPENJPA-159
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-159
>             Project: OpenJPA
>          Issue Type: Sub-task
>          Components: jdbc, kernel
>            Reporter: Patrick Linskey
>            Assignee: Michael Dick
>
> OpenJPA occasionally needs to perform work in a non-business transaction (see AbstractJDBCSeq.java). In a transactional environment, one way that this is achieved is by suspending the current JTA transaction, starting a new one, doing the work, cleaning up the new tx, and resuming the original one. Some environments do not allow direct transaction control, but mechanisms such as stateless session beans can often be used to kick off atomic operations that should execute in a separate transaction.
> We could easily add ManagedRuntime.executeInNewTransaction(Runnable) that captured this slightly-coarser-grained transaction control. The default implementation could simply do  suspend(), begin(), invoke Runnable.run(), commit()/rollback(), resume().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.