[SCB-669] Fix List response body deserialization problem

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: service-center-1.0.0-m2
• Assignee: Haishi Yao
• Reporter: Haishi Yao
• Created: 14/Jun/18 04:53
• Updated: 20/Jun/18 15:44
• Resolved: 20/Jun/18 15:44

Description

When a provider has a rest operation whose response is List<Pack>, and the type Pack is like below

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;
}

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>.

Issue Links

• links to: GitHub Pull Request #768