title: Python SOAP WSDL works in SOAPpy but not ZSI or zeep
body: <p>I need a python SOAP library that can handle multipart attachments. My understanding is that this is not supported by SOAPpy or suds but that it is supported by ZSI and zeep. However, while SOAPpy works just fine with the WSDL file that I need to use, ZSI and zeep give me errors. Here is the WSDL file: <a href="http://nva1wss.webex.com/nbr/services/NBRStorageService?wsdl" rel="nofollow noreferrer">http://nva1wss.webex.com/nbr/services/NBRStorageService?wsdl</a>. I opened the file in SoapUI and used the "Check WSI Compliance" option and it passed all of the checks.</p>
  
  <p>Here are my errors:</p>
  
  <p>zeep.exceptions.NamespaceError: Unable to resolve type {NBRStorageService}DataHandler. No schema available for the namespace u'NBRStorageService'.</p>
  
  <p>ZSI.generate.WsdlGeneratorError: failed to find import for schema "NBRStorageService"possibly missing @schemaLocation attribute.</p>
  
  <p>----Updated Info----</p>
  
  <p>Based on the verbose output from zeep I believe that the problem with the WSDL is that it uses a data type that zeep is unable to resolve in the schema document at <a href="http://schemas.xmlsoap.org/soap/encoding/" rel="nofollow noreferrer">http://schemas.xmlsoap.org/soap/encoding/</a>. Here is the data type definition in the WSDL:</p>
  
  <pre><code>&lt;wsdl:types&gt;
      &lt;schema xmlns="http://www.w3.org/2001/XMLSchema"
      targetNamespace="https://nva1wss.webex.com/nbr/services/NBRStorageService"&gt;
          &lt;import namespace="NBRStorageService"/&gt;
          &lt;import namespace="http://schemas.xmlsoap.org/soap/encoding/"/&gt;
          &lt;complexType name="ArrayOf_tns1_DataHandler"&gt;
              &lt;complexContent&gt;
                  &lt;restriction base="soapenc:Array"&gt;
                      &lt;attribute ref="soapenc:arrayType"
                      wsdl:arrayType="tns1:DataHandler[]"/&gt;
                  &lt;/restriction&gt;
              &lt;/complexContent&gt;
          &lt;/complexType&gt;
      &lt;/schema&gt;
  &lt;/wsdl:types&gt;
  </code></pre>
  
  <p>This WSDL appears to have been generated with Apache Axis 1.4. </p>
  
  <p>Any ideas on how to work around this? Or if anyone has any specific recommendations for server-side changes, I cannot make them, but I can certainly communicate them to the developers who handle the server. </p>
  
  <p>Thank you!</p>