on 09-09-2010 4:04 PM
Dear PI experts,
our partner provided a WSDL with the following definition (I modified it to keep it simple and showing the principles)
<wsdl:message name="nameOfMessage">
<wsdl:part element="part1" name="header" />
<wsdl:part element="part2" name="parameters" />
<wsdl:part element="part3" name="attachment" />
</wsdl:message>
After importing this WSDL in ESR, I found the following definition on tab 'WSDL':
<xsd:complexType name="nameOfMessage">
<xsd:sequence>
<xsd:element name="header" type="authentication" />
<xsd:element name="parameters" type="businessDatal" />
<xsd:element name="attachment" type="Binary" />
</xsd:sequence>
</xsd:complexType>
When creating the request message in PI it looks as follows:
<nameOfMessage>
<header/>
<parameters/>
<attachment/>
</nameOfMessage>
However our WebService provider expects the following:
<soap:env>
<authentication/>
<parameters/>
<attachment/>
</soap:env>
When using SoapUI and importing the WSDL the request message looks as expected by the web service provider and the part names are resolved.
I could try to convert the request using XSLT but this does not seem to be a best practice approach.
Do you have any advice on how to handle this issue?
Thank you very much.
Hi Florian,
I modified some WS to be handled by another systems, and sometimes, when the SOAP adapter is involved, you send a Request to PI (that has NOT the same structure, than the declared in the MM) but it takes the req. anyway.
Did you try sending a request?
Juan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.