Author |
Message
|
infotainment |
Posted: Thu Aug 18, 2016 11:33 pm Post subject: IIB: Error in create SOAP Message Model based on WSDL |
|
|
Apprentice
Joined: 18 Apr 2016 Posts: 41
|
Dear Team,
We are trying to create Message Model based on a SOAP WSDL.
WSDL is correctly importing and working in SOAPUI. However it throws validation errors while importing in IBM Integration Toolkit V10.0.0.5
Below is the WSDL:
Code: |
<wsdl:definitions name="ETradeService" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="http://10.222.20.61/etrade/ETradeService.svc?xsd=xsd0" namespace="http://tempuri.org/"/>
<xsd:import schemaLocation="http://10.222.20.61/etrade/ETradeService.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
<xsd:import schemaLocation="http://10.222.20.61/etrade/ETradeService.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ETRADE"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="LC">
<wsdl:part name="parameters" element="tns:LC"/>
</wsdl:message>
<wsdl:message name="LC_Headers">
<wsdl:part name="header" element="tns:header"/>
</wsdl:message>
<wsdl:message name="RESPONSE">
<wsdl:part name="parameters" element="tns:RESPONSE"/>
</wsdl:message>
<wsdl:message name="RESPONSE_Headers">
<wsdl:part name="header" element="tns:header"/>
</wsdl:message>
<wsdl:message name="AmendLC">
<wsdl:part name="parameters" element="tns:AmendLC"/>
</wsdl:message>
<wsdl:message name="AmendLC_Headers">
<wsdl:part name="header" element="tns:HEADER"/>
</wsdl:message>
<wsdl:portType name="ETradeServiceInterface">
<wsdl:operation name="InitiateLC">
<wsdl:input wsaw:Action="http://tempuri.org/ETradeServiceInterface/InitiateLC" name="LC" message="tns:LC"/>
<wsdl:output wsaw:Action="http://tempuri.org/ETradeServiceInterface/InitiateLCResponse" name="RESPONSE" message="tns:RESPONSE"/>
</wsdl:operation>
<wsdl:operation name="AmendLC">
<wsdl:input wsaw:Action="http://tempuri.org/ETradeServiceInterface/AmendLC" name="AmendLC" message="tns:AmendLC"/>
<wsdl:output wsaw:Action="http://tempuri.org/ETradeServiceInterface/AmendLCResponse" name="RESPONSE" message="tns:RESPONSE"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="BasicHttpBinding_ETradeServiceInterface" type="tns:ETradeServiceInterface">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="InitiateLC">
<soap:operation soapAction="http://tempuri.org/ETradeServiceInterface/InitiateLC" style="document"/>
<wsdl:input name="LC">
<soap:header message="tns:LC_Headers" part="header" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output name="RESPONSE">
<soap:header message="tns:RESPONSE_Headers" part="header" use="literal"/>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="AmendLC">
<soap:operation soapAction="http://tempuri.org/ETradeServiceInterface/AmendLC" style="document"/>
<wsdl:input name="AmendLC">
<soap:header message="tns:AmendLC_Headers" part="header" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output name="RESPONSE">
<soap:header message="tns:RESPONSE_Headers" part="header" use="literal"/>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="ETradeService">
<wsdl:port name="BasicHttpBinding_ETradeServiceInterface" binding="tns:BasicHttpBinding_ETradeServiceInterface">
<soap:address location="http://10.222.20.61/etrade/ETradeService.svc"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions> |
|
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Aug 19, 2016 12:02 am Post subject: Re: IIB: Error in create SOAP Message Model based on WSDL |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
infotainment wrote: |
<xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="http://10.222.20.61/etrade/ETradeService.svc?xsd=xsd0" namespace="http://tempuri.org/"/>
<xsd:import schemaLocation="http://10.222.20.61/etrade/ETradeService.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
<xsd:import schemaLocation="http://10.222.20.61/etrade/ETradeService.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ETRADE"/>
|
do you have the XSD's locally stored in the Broker Toolkit?
I've always copied remotely located XSD's to my system and modified the WSDL to point to their location.
This might be the issue.
Please tell us exactly what validation errors you are seeing?
Without this, we are guessing. There should be some indication in the Toolkit. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
infotainment |
Posted: Fri Aug 19, 2016 1:15 am Post subject: |
|
|
Apprentice
Joined: 18 Apr 2016 Posts: 41
|
Quote: |
Please tell us exactly what validation errors you are seeing? |
WSDL: The 'RESPONSE' element referenced by the Parameters part cannot be resolved.
You can reproduce by importing WSDL shared.
Quote: |
do you have the XSD's locally stored in the Broker Toolkit? |
Importing WSDL using Message Model approach. Exported WSDL is on local system. |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Aug 19, 2016 1:25 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
I said 'XSD' not WSDL.
That is why I referenced part of the WSDL that you posted.
THe WSDL tries to load the XSD's from 10.222.20.61
Get them into the same directory as the Locally stored WSDL amd modify the WSDL to temove those internet references.
Then try the import again.
If needed, import the XSD's first. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
infotainment |
Posted: Fri Aug 19, 2016 1:53 am Post subject: |
|
|
Apprentice
Joined: 18 Apr 2016 Posts: 41
|
Quote: |
Get them into the same directory as the Locally stored WSDL amd modify the WSDL to temove those internet references.
Then try the import again.
If needed, import the XSD's first |
I did but issue did not resolve.
Then I manually corrected issue in wsdl imported. It was creating same name in wsdl:output tag and once I correct the duplication issue, its working now. |
|
Back to top |
|
 |
|