Haishi Yao created SCB-2031:
-------------------------------
Summary: There is a problem in the mapping logic between pojo
consumer meta and swagger operation
Key: SCB-2031
URL: https://issues.apache.org/jira/browse/SCB-2031
Project: Apache ServiceComb
Issue Type: Bug
Components: Java-Chassis
Affects Versions: java-chassis-2.1.0, java-chassis-2.0.2,
java-chassis-2.0.1, java-chassis-2.0.0
Reporter: Haishi Yao
Assignee: Haishi Yao
There are two RPC consumer scenario should be covered.
1. There are two method in the pojo interface with the same method name
pointing to the two different provider swagger operations:
{code:java}
interface OptionalIntf {
@ApiOperation(value = "", nickname = "sayHi")
String sayHello(Long index);
@ApiOperation(value = "", nickname = "sayHello")
String sayHello(String name);
}
{code}
2. There are two method in the pojo interface with different method name
pointing to the same provider swagger operation:
{code:java}
interface OptionalIntf {
@ApiOperation(value = "", nickname = "sayHi")
String sayHello(Long index);
@ApiOperation(value = "", nickname = "sayHi")
CompletableFuture<ResponseEntity<String>> sayHelloEntityAsync(Long index);
}
{code}
In order to achieve such feature, the mapping relationship should be from
consumer pojo method to provider swagger operationId, instead in the reverse
direction.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
