Bo Li created SC-47:
-----------------------
Summary: As a SDK user, I want to consume or produce not concrete
data type
Key: SC-47
URL: https://issues.apache.org/jira/browse/SC-47
Project: Apache ServiceComb
Issue Type: Sub-task
Components: Java-Chassis
Reporter: Bo Li
generally, input parameters or response data type must be concrete, it's a good
practice.
but some times, developers can not make it concrete, eg:
1.config items transfer, we can not make every config item to be a operation.
2.smart home terminal report data, data type is determined by terminal type.
so outside of "good practice", we should provide a mechanism to allow
developers to consume or produce not concrete data type.
what is "concrete data type":
1.Map<String, Object>
2.List<Object>
3.interface or abstract class
requirements:
1.producer: if found not concrete data type, and the operation not annotated by
xxx annotation, then will print warning log.
2.Map<String, Object>, swagger type is "json-map"
3.List<Object>, swagger type is "json-array"
4.highway server encode data to be a json string, highway client decode json
string to map or list
depends on protoStuff mechanism, not know how to do now.
5.if use interface or abstract class, then must customize jackson
JsonSerializer/JsonDeserializer
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
