[
https://issues.apache.org/jira/browse/SCB-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated SCB-1386:
------------------------------
Description:
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.
was:
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.
To support the old behavior of SagaStart, we need to add an option to disable
sending the Saga end event.
> 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
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
