none
The required WSDL extension element 'multipartRelated' from namespace 'http://schemas.xmlsoap.org/wsdl/mime/' was not handled. RRS feed

  • Question

  • VS 2013, Add Service Reference, http://iqws.intechiq.com/IQOffice2.wsdl

    I get:

    Warning 107 Custom tool warning: Cannot import wsdl:binding
    Detail: The required WSDL extension element 'multipartRelated' from namespace 'http://schemas.xmlsoap.org/wsdl/mime/' was not handled.
    XPath to Error Source: //wsdl:definitions[@targetNamespace='http://intechsolutions.com.au/soap2/']/wsdl:binding[@name='iqoffice2'] \Path\To\Reference.svcmap

    The offending fragment of the 'binding' element is an 'operation' with an 'output' from the 'http://schemas.xmlsoap.org/wsdl/mime/' namespace.

    <operation name="PolygonSearch">
    <SOAP:operation soapAction=""/>
    <input>
    <SOAP:body parts="parameters" use="literal"/>
    </input>
    <output>
    <MIME:multipartRelated>
    <MIME:part>
    <SOAP:body parts="parameters" use="literal"/>
    </MIME:part>
    <MIME:part>
    <MIME:content part="attachments" type="application/x-gzip"/>
    </MIME:part>
    </MIME:multipartRelated>
    </output>
    </operation>


    What are my options?  The answer to a similar question on this forum from 2009 claims without elaboration that 'WCF does not support MIME'.  I don't particularly need the 'PolygonSearch' operation for my use of the service.  I'd prefer not to have to hack up my own private local copy of the WSDL.  (It's 2014 now, hey.)

    Monday, April 21, 2014 1:05 PM

All replies

  • Hi,
    Warning 107 Custom tool warning: Cannot import wsdl:binding
    Detail: The required WSDL extension element 'multipartRelated' from namespace 'http://schemas.xmlsoap.org/wsdl/mime/' was not handled.
    XPath to Error Source: //wsdl:definitions[@targetNamespace='http://intechsolutions.com.au/soap2/']/wsdl:binding[@name='iqoffice2']
    \Path\To\Reference.svcmap

    When occuring the above problem, then (usually) you have nothing to worry about. What they mean is that your WSDL contains a binding which uses HTTP Post transport.

    For more information, please try to refer to:
    http://webservices20.blogspot.com/2009_02_01_archive.html .

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, April 22, 2014 2:51 AM
    Moderator
  • Hi Amy,

    With that encouragement, I re-attempted adding the service reference in a standalone project.  

    The warning:

       The required WSDL extension element 'multipartRelated' from namespace 'http://schemas.xmlsoap.org/wsdl/mime/' was not handled.

    is followed by:

       There was an error importing a wsdl:binding that the wsdl:port is dependent on.

    Although these are 'warnings' rather than 'errors', the practical effect of this is that Visual Studio fails to write an <endpoint/> element under configuration/system.serviceModel/client in the project's .config file.

    But if I provide the <endpoint/> declaration myself, it seems I can actually use the generated proxy and stubs  (at least for operations other than PolygonSearch) despite those warnings.

    In this case, VS2013's failure to write to the .config file is due SOLELY to the presence of the MIME namespace in the operation definition, since if I manually hack a local copy of the WSDL to remove the offending PolygonSearch operation from the SOAP binding and definition, then Visual Studio *does* put the <endpoint/> into the .config file.

    Also, unlike the blog post you referenced, here VS2013's failure to handle the binding DOES matter, since it's the ONLY binding (it's not an 'optional' HTTP POST binding).

    I am yet to try whether, when I process the original WSDL and supply the <endpoint/> to the .config file manually, the PolygonSearch operation actually works.  I suspect that it will not.

    And it's a long way from 'add a Service Reference and start coding', which is what I pay $ for to subscribe to MSDN.  Would you regard the above as a bug/flaw with VS2013?


    • Edited by dtbullock Tuesday, April 22, 2014 4:35 AM typo
    Tuesday, April 22, 2014 4:34 AM
  • I suppose to summarise, in SOAP-speak, what we're looking at here is:

    a) the WSDL is using a 'SOAP with attachments' binding (hence the MIME multipart)

    b) WCF doesn't support 'SOAP with attachments'  bindings? (not being much interested in interoperability, obviously)  ??

    c) Visual Studio has a bad failure mode when the only binding is a 'SOAP with attachments' binding, and processing of that binding fails (without being so bold as to say in the warning that 'SOAP with attachments' is 'not supported'.)

    Does that seem to summarise the issue here?

    Tuesday, April 22, 2014 4:44 AM