WSDL Won't Load

I can not get this wsdl to load. Why?
Hi Jeff,

The URL is unreachable. Can you upload the wsdl as a file please?
<definitions xmlns:xsd="" xmlns:tns="mtvnCICustPrflWSV2" xmlns:soap=""
targetNamespace="mtvnCICustPrflWSV2" name="mtvnCICustPrflWSV2" xmlns="">

<documentation xmlns="">Connectware Web Service Interface</documentation>

<xsd:import schemaLocation="./CICustPrflWSV2SvcReq.xsd" namespace="mtvnCWCICustPrflSvcReq" />
<xsd:import schemaLocation="./CICustPrflWSV2SvcRes.xsd" namespace="mtvnCWCICustPrflSvcRes" />

<message name="CICustPrflMtvnSvcReqMsg">
<documentation xmlns="" />
<part name="messagePart" element="import0:CICustPrflMtvnSvcReq" />
<message name="CICustPrflMtvnSvcResMsg">
<documentation xmlns="" />
<part name="messagePart" element="import1:CICustPrflMtvnSvcRes" />

<portType name="mtvnCWCICustPrflWSV2Interface">
<documentation xmlns="">CICustPrflWSV2</documentation>
<operation name="CICustPrfl">
<documentation xmlns="" />
<input message="tns:CICustPrflMtvnSvcReqMsg" />
<output message="tns:CICustPrflMtvnSvcResMsg" />

<binding name="mtvnCWCICustPrflWSV2" type="tns:mtvnCWCICustPrflWSV2Interface">
<soap:binding transport="" style="document" />
<operation name="CICustPrfl">
<soap:operation soapAction="CICustPrflWSV2:CICustPrflMtvnSvcReqMsg" style="document" />
<soap:body use="literal" />
<soap:body use="literal" />

<service name="mtvnCWCICustPrflWSV2">
<port name="mtvnCWCICustPrflWSV2Port" binding="tns:mtvnCWCICustPrflWSV2">
<soap:address location="" />

Hi Jeff,

I think the problem is the xsd imports you have on the wsdl. Try to make a single wsdl without import files and with the complete type definition. If you can't do this I think the best option you have is to import this functionality through an extension.
This is a client provided wsdl so I can not change it.
Why can it not handle the imports?
Hi again Jeff,

Correct me if I'm wrong but you only need the wsdl to create the webreference interface. With that said, you can create a local version of this wsdl and import it to service studio, say from c:\myversion.wsdl.

As to why the OutSystems Platform doesn't import the xsd I really have no good answer to give you but I can tell you this. Try to import the wsdl and then submit feedback back to OutSystems support or, alternatively, send the wsdl to They'll be pleased to get this feedback and for sure get back to you.
I am experiencing this problem in the version i uploaded yesterday. Is there any resolution? I believe that this type of wsdl is always generated from a java bean based web service when the arguments are bean objects. SOAPUI gets it right, and wondering why OutSystems can't. I can probably work around it by creating a flattened wsdl and importing it, but since a large part of my business is showing how tools like OutSystem can connect to standard web services, it exposes a weakness that requires using external tools to mitigate.

FICO is a partner of OutSystems
Hi George.
Can you post the WSDL you are trying to import so that I can take a look at it? 
If you prefer not to share the WSDL you can instead send it to 
This is a good tool to help test WSDL:

After talking with George we realized that XSD-inferred structures were actually imported, but with a slightly different structure from what George and I had expected. Everything worked after we realized that though!.

João Proença