biedongbin opened a new pull request, #8027:
URL: https://github.com/apache/incubator-seata/pull/8027

   
   <!--
       Licensed to the Apache Software Foundation (ASF) under one or more
       contributor license agreements.  See the NOTICE file distributed with
       this work for additional information regarding copyright ownership.
       The ASF licenses this file to You under the Apache License, Version 2.0
       (the "License"); you may not use this file except in compliance with
       the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
       
       Unless required by applicable law or agreed to in writing, software
       distributed under the License is distributed on an "AS IS" BASIS,
       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
       See the License for the specific language governing permissions and
       limitations under the License.
   -->
   <!-- Please make sure you have read and understood the contributing 
guidelines -->
   
   - [ Y] I have read the 
[CONTRIBUTING.md](https://github.com/apache/incubator-seata/blob/2.x/CONTRIBUTING.md)
 guidelines.
   - [y ] I have registered the PR 
[changes](https://github.com/apache/incubator-seata/tree/2.x/changes).
   
   ### Ⅰ. Describe what this PR did
   
   Add action status report mechanism to handle empty compensation and 
suspension issues in SAGA annotation mode.
   
   Changes:
   
   Add configuration key CLIENT_SAGA_ACTION_STATUS_REPORT_ENABLE (default false)
   Add action status constants: ACTION_STATUS, ACTION_STATUS_SUCCESS, 
ACTION_STATUS_FAILED
   Add getActionStatus/setActionStatus methods in BusinessActionContext
   Report action status (success/failed) after prepare method execution in 
non-CommonFence mode
   Add Hook invocation before/after compensation in 
SagaAnnotationResourceManager
   Business layer can implement TccHook interface and read actionStatus in 
beforeTccRollback() to decide compensation behavior.
   
   
   ### Ⅱ. Does this pull request fix one issue?
   <!-- If that, add "fixes #xxx" below in the next line, for example, fixes 
#97. -->
   
   fixes #7840 
   
   ### Ⅲ. Why don't you add test cases (unit test/integration test)? 
   
   
   ### Ⅳ. Describe how to verify it
   
   
   ### Ⅴ. Special notes for reviews
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to