[jira] [Updated] (SCB-669) Fix List response body deserialization problem

["YaoHaishi (JIRA)" <ji...@apache.org>]

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

YaoHaishi updated SCB-669:
--------------------------
    Attachment: invokeProviderDirectly.jpg
                invokeViaEdgeService.jpg

> Fix List response body deserialization problem
> ----------------------------------------------
>
>                 Key: SCB-669
>                 URL: https://issues.apache.org/jira/browse/SCB-669
>             Project: Apache ServiceComb
>          Issue Type: Bug
>            Reporter: YaoHaishi
>            Assignee: YaoHaishi
>            Priority: Major
>             Fix For: service-center-1.0.0-m2
>
>         Attachments: invokeProviderDirectly.jpg, invokeViaEdgeService.jpg
>
>
> When a provider has a rest operation whose response is List<Pack>, and the type Pack is like below
> {code:java}
> public class Pack{
>   private String name;
>   private int i;
>   // PackageProp is a type defined by user, and it only contains simple java type
>   private List<PackageProp> packagePropList;
> }
> public class PackageProp{
>   private String name;
>   private int j;
>   private String prop;
> }
> {code}
> We can use postman to invoke the rest operation directly and it works well. But if we invoke this operation via EdgeService, the response body will be deserialized in edge unproperly. The edge treat the response List<Pack> as List<PackageProp>.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)