[jira] [Resolved] (SCB-1386) Support to send out SagaEnd event in other method

["Willem Jiang (Jira)" <ji...@apache.org>]

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

Willem Jiang resolved SCB-1386.
-------------------------------
    Resolution: Fixed

Applied patch into master branch.

> Support to send out SagaEnd event in other method
> -------------------------------------------------
>
>                 Key: SCB-1386
>                 URL: https://issues.apache.org/jira/browse/SCB-1386
>             Project: Apache ServiceComb
>          Issue Type: New Feature
>          Components: Saga
>    Affects Versions: pack-0.5.0
>            Reporter: José Cardoso
>            Assignee: Willem Jiang
>            Priority: Major
>             Fix For: pack-0.5.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In an async environment (ex: microservices architecture communicating via messaging systems) it is important to control when the saga ends. Therefore, I propose a new annotation - @SagaEnd - to have the possibility to explicitly end the Saga, which will also allow the triggering of the compensation methods in case of failure. 
> *NOTE from willem*
> To support the old behavior of SagaStart, we need to add an option to disable sending the Saga end event.
> To avoid the aspect class conflict, I didn't introduce @SagaEnd annotation, I just introduced sendingSagaEnd attribute to SagaStart and Compensable this two annotations class to control the SagaEnd event sending.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)