[
https://issues.apache.org/jira/browse/SCB-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889517#comment-16889517
]
Willem Jiang commented on SCB-1386:
-----------------------------------
I think we can address it by introducing a new attribute in SagaStart
annotation, which means Omega doesn't send SagaEnd event once the SagaStart
method is executed. It can give a chance to the customer to end the local
transaction and Saga Transaction as they want. I'm not sure if it exports too
much detail to the client and we may also introduce a timeout mechanism in case
of the async invocation never send response back.
> @SagaEnd annotation
> -------------------
>
> 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
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
