cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Dear Experts,

I'm developing a solution that uses an external SOAP service. But when I upload the file WSDL, it showed the error.

Could you please tell me how to fix this error?

Thanks and Best Regards

Truong

0 Likes
View Entire Topic
HorstSchaude
Product and Topic Expert
Product and Topic Expert

Hello Truong,

Sorry, I've overlooked that button. 😞

It is exactly as andy.blankley mentioned above:

The messages in the WSDL file consist of 3 parts:

  • parameters
  • technicalAddress
  • activationHeader

Example:

 <wsdl:message name="getBankCertificate">
  <wsdl:part name="parameters" element="tns:getBankCertificate"/>
  <wsdl:part name="technicalAddress" element="tns:technicalAddress"/>
  <wsdl:part name="activationHeader" element="tns:activationHeader"/>
 </wsdl:message>
 <wsdl:message name="getBankCertificateResponse">
  <wsdl:part name="parameters" element="tns:getBankCertificateResponse"/>
  <wsdl:part name="technicalAddress" element="tns:technicalAddress"/>
  <wsdl:part name="activationHeader" element="tns:activationHeader"/>
 </wsdl:message>
...

This is not supported.

Only message like this:

- <wsdl:message name="LocationByIDQuery_sync">
  <wsdl:part name="LocationByIDQuery_sync" element="n1:LocationByIDQuery_sync" />
  </wsdl:message>
- <wsdl:message name="LocationByIDResponse_sync">
  <wsdl:part name="LocationByIDResponse_sync" element="n1:LocationByIDResponse_sync" /> 
  </wsdl:message>
- <wsdl:message name="StandardFaultMessage">
  <wsdl:part name="StandardFaultMessage" element="n2:StandardFaultMessage" /> 
  </wsdl:message>

Sorry,
. Horst

truonglv
Participant
0 Likes

Thanks Horst,

But these files are from a Provider, that 's mean we can not edit their content. So do you have any idea here for this integration, any work around?

Thanks

Truong