Support for transaction/compensation
------------------------------------
Key: TUSCANY-1667
URL: https://issues.apache.org/jira/browse/TUSCANY-1667
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Environment: All
Reporter: haleh mahbod
I am creating this JIRA based on email thread below from Jeff Anderson
(Deloitte).
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01683.html
Text of the requirement:
transaction/compensation-I realize that the SCA specification is little more
vague/not finalized concerning this, however this is one of the most important
features requested from our client. Again I envision using the policy
framework to define a transaction setting such as @NotRequired,@Supported etc.
For local bindings this would simply allow the typical distributed transaction
mechanisms to reverse any resources held within a transaction lock. For a more
traditional remote Web services environment where resource control is the
exception rather than the rule, an additional annotation of @compensator would
allow service developer to declare the compensation transaction required
whenever the appropriate binding container declares that a part of the
transaction has failed. Again I believe the mechanisms of the model would vary
depending on the binding mechanism used. For remote , WSI-Basic interoperable
services can use WS -- atomic. For local, services would have the option of
leveraging the the compensation model or integrate into the existing container
distributed transaction manager. I realize that people In Tuscany are hesitant
to start working on this kind of work until the spec has more details around
transactions. However I believe the majority of this implementation could go
forward without being impacted by the spec. Annotations may change but the
mechanisms for handling transactions are fairly well-known and can be
stabilized early on.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
