[jbossts-issues] [JBoss JIRA] Resolved: (JBTM-560) provide distinct beforeCompletion phase in subordinate tx API

[Mark Little (JIRA)]

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

Mark Little resolved JBTM-560.
------------------------------

    Resolution: Done


Synchronizations can now be driven independently of 2PC or within 2PC (as existed prior to this change.)

> provide distinct beforeCompletion phase in subordinate tx API
> -------------------------------------------------------------
>
>                 Key: JBTM-560
>                 URL: https://jira.jboss.org/jira/browse/JBTM-560
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JCA, JTA, JTS, Transaction Core
>    Affects Versions: 4.6.1
>            Reporter: Jonathan Halliday
>            Assignee: Mark Little
>             Fix For: 4.7.0
>
>
> A subordinate transaction exposes an API that allows the prepare and commit/rollback phases of the termination protocol to be driven separately, much like a resource. This maps well to the JCA Terminator API.
> However, it poses difficulties for beforeCompletion work. With the current API these must be done at prepare time, but should run in transaction context, which the prepare does not necessarily do. They may also take a long time (e.g. large hibernate context flushes) which can cause timeout issues.
> It would be useful to extend the XATerminator so that it exposes the before (and maybe the after, although that's less important) synchronization phases as separate operations. Care should be taken that this does not break usage done though the existing JCA API, which would not allow the new methods to be used directly.

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