[jbossts-issues] [JBoss JIRA] (JBTM-1472) Initial version of Compensations API
Paul Robinson (JIRA)
jira-events at lists.jboss.org
Tue May 7 06:59:53 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Robinson updated JBTM-1472:
Priority: Critical (was: Major)
> Initial version of Compensations API
> Key: JBTM-1472
> URL: https://issues.jboss.org/browse/JBTM-1472
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M3
> Original Estimate: 2 weeks
> Time Spent: 1 week, 6 hours
> Remaining Estimate: 3 days
> We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS).
> It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market.
> This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API.
> # Investigate existing WS-BA APIs
> ## Try code examples if possible
> # Produce an initial list of features that should be covered by the API
> # Create a simple implementation backed by WS-BA.
> Implementation work, to complete this issue:
> # Manage lifecycle of transaction via the @Compensatable annotation
> # Allow Compensation and Completion handlers to be registered via annotations
> # Mechanism for allowing application to mark the transaction as CompensateOnly
> # Document the API
> # Merge into Narayana code base
> # OOTB support in WildFly
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
More information about the jbossts-issues