You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "Zheng Feng (JIRA)" <ji...@apache.org> on 2018/10/31 06:03:00 UTC
[jira] [Commented] (SCB-836) Support the nesting SagaStart
[ https://issues.apache.org/jira/browse/SCB-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669660#comment-16669660 ]
Zheng Feng commented on SCB-836:
--------------------------------
NOTE from the spec of LRA
{noformat}
Note that there is no annotation to directly cancel a closed nested LRA and the Java LRAClient api must be used for this purpose if required.
{noformat}
So we need these client APIs to talk to the alpha server directly ?
> Support the nesting SagaStart
> -----------------------------
>
> Key: SCB-836
> URL: https://issues.apache.org/jira/browse/SCB-836
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Saga
> Reporter: Willem Jiang
> Priority: Major
>
> We can take the [nesting-lras|https://github.com/eclipse/microprofile-lra/blob/master/spec/src/main/asciidoc/microprofile-lra-spec.adoc#323-nesting-lras] from the microprofile as an example.
> An activity can be scoped within an existing Saga using the @SagaStart annotation. Invoking a method marked with this annotation will start a new Saga whose outcome depends upon whether the enclosing Saga is closed or cancelled.
> * If the nested Saga is closed but the outer Saga is cancelled then the participants registered with the nested Saga will be told to compensate.
> * If the nested Saga is cancelled the outer Saga can be still closed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)