xsi:type in generated XML causes it not to validate/load into: visual studio or Mindreef SOAPscope

• Key: TUSCANY-1297
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: Matthew Peters
• Component/s: C++ SDO
• Affects Version/s: Cpp-Next
• Fix Version/s: Cpp-Next

Description

We use SDO to build and generate WSDL. We use the standard WSDL and SOAP schemas (schemata?) to build the model then add port, operation, binding etc. elements, then serialise the lot to XML. There are occasional xsi:type attributes in the serialised XML which cause the WSDL not to validate or load in visual studio. Here is a snippet from WSDL that we have generated in this way:

<binding name="Labnet_API_LabnetOnline_001_ImplementationBinding"
type="tns2:Labnet_API_LabnetOnline_001_ImplementationPortType">
    <operation name="getRestorations">
      <input>
        <tns3:body xsi:type="tns3:tBody" use="literal"/>
      </input>
      <output>
        <tns3:body xsi:type="tns3:tBody" use="literal"/>
      </output>

      <tns3:operation xsi:type="tns3:tOperation" soapAction=""/>
    </operation>
<tns3:binding xsi:type="tns3:tBinding"
transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
  </binding>

These xsi:type attributes cause this WSDL to fail to load. I quote one of our users:

> MS Visual Studio (I'm using Visual Web Dev 2005 Express Edition) will
> not import a SCA generated WSDL. It complains that it does not validate
> because of the following element attributes:

> xsi:type="tns3:tBody" of <tns3:body>
> xsi:type="tns3:tAddress" of <tns3:address>

> Stripping out these attributes resolved the VS WSDL import problem.

and a different bug report but the same problem:

> WSDL generated does not validate (ran against the oXygen editor and
Mindreef SOAPscope).