You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@servicecomb.apache.org by "Eric Lee (JIRA)" <ji...@apache.org> on 2017/12/20 02:20:00 UTC

[jira] [Updated] (SC-26) serial service invocations

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

Eric Lee updated SC-26:
-----------------------
    Description: 
*Given*
aggregator configured with serial service invocations in a configuration file
*When*
a request goes through services in order a -> b -> c -> d without transformation of data
*Then*
aggregator invokes the services a/b/c/d in order and returns the response from service d

  was:
Given
aggregator configured with serial service invocations in a configuration file
When
a request goes through services in order a -> b -> c -> d without transformation of data
Then
aggregator invokes the services a/b/c/d in order and returns the response from service d


> serial service invocations
> --------------------------
>
>                 Key: SC-26
>                 URL: https://issues.apache.org/jira/browse/SC-26
>             Project: Apache ServiceComb
>          Issue Type: Sub-task
>          Components: Java-Chassis
>            Reporter: Eric Lee
>
> *Given*
> aggregator configured with serial service invocations in a configuration file
> *When*
> a request goes through services in order a -> b -> c -> d without transformation of data
> *Then*
> aggregator invokes the services a/b/c/d in order and returns the response from service d



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)