This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git
commit 0742bf38cc795fb89c421fcf2d60df70fb0e208c
Author: 自然 <natur...@qq.com>
AuthorDate: Fri Sep 6 19:55:02 2019 +0800
Update interface-constraints.md
---
java-chassis-reference/en_US/build-provider/interface-constraints.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/java-chassis-reference/en_US/build-provider/interface-constraints.md
b/java-chassis-reference/en_US/build-provider/interface-constraints.md
index c00e402..3506603 100644
--- a/java-chassis-reference/en_US/build-provider/interface-constraints.md
+++ b/java-chassis-reference/en_US/build-provider/interface-constraints.md
@@ -8,7 +8,7 @@ For example:
```java
public Person query(String id);
public Object query(String id);
-public class Person {String name;}
+public Person query(String name);
```
Obviously, if API 1 is called, we know that an ID parameter of String type
needs to be transferred. The returned value is of Person type, which contains a
string-typed name parameter. If API 2 is called, we do not know how to process
the returned value, and need to refer to documents provided by the service
provider. API 2 is developed in the perspective of RPC developers.
