| Author |
Message
|
| Vinayak.Satapute |
 Posted: Wed Aug 14, 2013 3:45 am Post subject: WSDL:element referenced by the Message part cannot be resolv |
 |
|
Acolyte
Joined: 20 Dec 2006
Posts: 70
|
I am trying to import the below the WSDL under the MessageSet Project.
but getting the below errors.
*******************Errors******************
1. WSDL: The 'AcknowledgeFacilityLimit' element referenced by the Message part cannot be resolved.
2. WSDL: The 'GetFacilityLimit' element referenced by the Message part cannot be resolved.
3. WSDL: The 'ProcessFacilityLimit' element referenced by the Message part cannot be resolved.
4. WSDL: The 'ShowFacilityLimit' element referenced by the Message part cannot be resolved.
5. XSD: The location 'GlobalLimitsService_InlineSchema1.xsd' has not been resolved
(I am trying to import the mentioned XSD (error 5 above) but that also generating errors.
Errors above 1 to 4, I have imported the mentioned types XSD under the message set but still the WSDL file below is having errors.
Appreciate your input to resolve this errors.
Thanks.
**********************WSDL FILE AS BELOW*************
| Code: |
<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions targetNamespace="http://www.nbad.com/GlobalLimitsService" xmlns="http://www.nbad.com/GlobalLimitsService" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:model="http://www.nbad.com/model" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<wsdl:documentation>
<wsdl:appinfo source="WMQI_APPINFO">
<MRWSDLAppInfo imported="true">
<generatedXSD location="GlobalLimitsService_InlineSchema1.xsd"/>
<binding hasEncoding="false" imported="true" name="GlobalLimitsBinding" originalBindingStyle="document"/>
</MRWSDLAppInfo>
</wsdl:appinfo>
</wsdl:documentation>
<wsdl:types>
<xsd:schema elementFormDefault="qualified" targetNamespace="http://www.nbad.com/model" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="GlobalLimitsService_InlineSchema1.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="GetFacilityLimit">
<wsdl:part element="model:GetFacilityLimit" name="Message"/>
</wsdl:message>
<wsdl:message name="ShowFacilityLimit">
<wsdl:part element="model:ShowFacilityLimit" name="Message"/>
</wsdl:message>
<wsdl:message name="ProcessFacilityLimit">
<wsdl:part element="model:ProcessFacilityLimit" name="Message"/>
</wsdl:message>
<wsdl:message name="AcknowledgeFacilityLimit">
<wsdl:part element="model:AcknowledgeFacilityLimit" name="Message"/>
</wsdl:message>
<wsdl:portType name="GlobalLimitsPortType">
<wsdl:operation name="GetFacilityLimit">
<wsdl:input message="GetFacilityLimit"/>
<wsdl:output message="ShowFacilityLimit"/>
</wsdl:operation>
<wsdl:operation name="ProcessFacilityLimit">
<wsdl:input message="ProcessFacilityLimit"/>
<wsdl:output message="AcknowledgeFacilityLimit"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="GlobalLimitsBinding" type="GlobalLimitsPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="GetFacilityLimit">
<soap:operation soapAction="http://www.nbad.com/GlobalLimitsService/GetFacilityLimit"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="ProcessFacilityLimit">
<soap:operation soapAction="http://www.nbad.com/GlobalLimitsService/ProcessFacilityLimit"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="GlobalLimitsService">
<wsdl:port binding="GlobalLimitsBinding" name="GlobalLimitsPort">
<soap:address location="http://localhost:7800/nbad/WADDR/GlobalLimitsService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions> |
[/img] |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Aug 14, 2013 3:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Simbu |
| Posted: Wed Aug 14, 2013 4:02 am Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| Vinayak, best practice is to have validated WSDL and XSDs in a Project or folder and import the wsdl into the message set. Please try this. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Aug 14, 2013 4:48 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
Which version of WMB/IIB are you using?
Probably best to quote the version in the 'v.r.m.f' format ( e.g. '8.0.0.2' ) so as not to provoke lancelotinc 
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 14, 2013 4:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kimbert wrote: |
| so as not to provoke lancelotinc |
He's already groweled once this thread.... 
Does the WSDL contain explicit imports for the XSDs which contain the unresolveable elements? Depending on version, a chicken soup solution could be to remove the import statements and let Toolkit work it out for itself.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Aug 14, 2013 5:12 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| kimbert wrote: |
Which version of WMB/IIB are you using?
Probably best to quote the version in the 'v.r.m.f' format ( e.g. '8.0.0.2' ) so as not to provoke lancelotinc |
Too funny kimbert ! You too Vitor !
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
