0x101011 commented on issue #9798:
URL: https://github.com/apache/apisix/issues/9798#issuecomment-1625203578
Yes Bro,
In some java web develop cases, we design api by RPC or ROA pattern. we
always try to POST a DTO Object request Parameters.
In many cases , the param not just contain BASIC Java Types : the Parent
Class DTO contains many sub Class DTO. it came to be nested Object.
`controller`:
```java
@PostMapping("/api/saveOrUpdate")
public Mono<String> saveOrUpdate(@RequestBody MetaDataDTO metaDataDto) {
return Mono.just(Constants.SUCCESS);
}
```
`request param`
```java
public class MetaDataDto {
private String id;
private String appName;
private String contextPath;
private String path;
private MetaConfigDTO metaconfig;
```
In Dubbo , the Provider Alway choose to define a Facade/API layer ,which
just contain all function interface and param DTO. this layer give to Consumer
to dependency .
such as：
`Facade/API layer`
```java
public interface HelloService {
public UserVerifyResponse verify(UserInfoRequest who);
}
```
So . in `Dubbo-Proxy-Plugin` it provide ability to parse HTTP -> Dubbo xrpc
. it really helpful for some Developed Online Dubbo Service ,for we can expose
dubbo service not to develop a Java Web Parsing Dubbo Layer.
But for many application online which we can not Expose it easy because
Parameter Type Problem.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
