Hi,
I have successfully imported a WSDL in ESR, provided by a third party.
The WSDL is a big complex hierarchical structure. The WSDL message is clearly visible in PI but the underneath full structure isn't.
The structure somewhat looks like below.
Message -> Element 1-> Visible in PI
Element 1 -> Element 2 -> Type 1 where Type 1 exists in target namespace 1 urn:www.client.com/------ ->Visible in PI
Type 1 -> Type 1 where Type 1 exists in target namespace 2http://schemas.datacontract.org/------->Not Visible in PI
namespace 3http://schemas.datacontract.org/------ uses the import namespace 2 and has Element 3 which is of Type 1 and the full structure underneath -> Not visible in PI
namespace 1, 2 & 3 are basically different types and appear as different tags under the <wsdl:types> segment.
The WSDL doesn't seem to have any reference to any external XSD / WSDL (No schemaLocation tag in WSDL and nothing also appears in the external reference tab in ESR). Also the WSDL is not a RPC one.
I have also imported the WSDL in SOAP UI but there also the same error persists.
The third party says that WSDL has been generated by dotnet application and validated and already consumed successfully by other applications.They have also provided some code to call the Web Service, which I think would not be applicable for PI.
I know it's a bit complicated to understand from above explanation but any idea on the possible cause of the issue or any workaround (No manual creation of Data type as the WSDL is quite big). The only difference I see here is that namespace 1 (visible) is client.com while the namespace 2 & 3 are schemas.datacontract.org (not visible). Can it be due to the fact that the namespace3 & namespace4 definitions are not accessible from PI as well as my local machine - A wild guess :-))
Also please let me know if any further details is required, thanks.