We are trying to create an API Proxy using a WSDL which has a local schema specified...
The local schema has the input and output types specified as complex types with Extension Bases..
When the API is created with REST to SOAP Policy components only the fields mentioned explicitly in Input/Output type in local schema are defined as Query Parameters...
The fields mentioned under the type for the extension base are skipped..
This leads to us to manually add these fields for all the 30 operations for the WSDL
e.g: Assume the following is the type of input element...
<xs:complexType name="RequestWrapper">
<xs:complexContent>
<xs:extension base="tns:ServiceRequestWrapper">
<xs:sequence>
<xs:element name="request" type="tns:AuthRequest"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
On creating an API with this input type only AuthRequest is mentioned in the Input of REST and the fields under ServiceRequestWrapper are lost...
Is there a better way out for this?
The way to process the WSDL in its entirety inculsive of extension base elements in WSDL Local Schema
LinkedIn
Twitter
