Be able to consume SOAP And/Or WSDL to generate XML Mappings

[9ParsonsB]

I find it a huge pain having to write serialization mappings for XML / SOAP services.

QuickType has saved me a huge amount of time with mappings for JSON and so I would like to propose that QuickType be extended to also support XML / SOAP and potentially WSDL

Input:

SOAP:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header/>
   <soapenv:Body>
      <SomeRequest>
         <SomeProperty>1</SomeProperty>
         <OtherProperty>Hello</OtherProperty>
      </SomeRequest>
   </soapenv:Body>
</soapenv:Envelope>

OR

WSDL:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions http:force="" name="ServiceOrEndpointName" targetNamespace="NameSpace" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="NameSpace" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:documentation>
        Documentation about the service
    </wsdl:documentation>
    <wsdl:types>
        <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
            <xs:element name="SomeRequest" type="SomeRequestType">
                <xs:annotation>
                    <xs:documentation>Some Documentation for this request</xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:complexType name="SomeRequestType">
                <xs:annotation>
                    <xs:documentation>Documentation about this type</xs:documentation>
                </xs:annotation>
                <xs:sequence>
                    <xs:element form="unqualified" name="SomeProperty" type="xs:int"/>
                    <xs:element form="unqualified" name="OtherProperty" type="xs:string"/>
                </xs:sequence>
            </xs:complexType>
        </xs:schema>
    </wsdl:types>
</wsdl:definitions>

Output:

C#:

namespace QuickType
{
    [SoapType("SomeRequestType")]
    public class SomeRequest
    {
        [SoapElement("SomeProperty")]
        public int SomeProperty { get; set; }

        [SoapElement("OtherProperty")]
        public string OtherProperty { get; set; }
    }

    public static class Converter
    {
        public static string SerializeObject<T>(T serialize)
        {
            var stringWriter = new StringWriter();
            new XmlSerializer(typeof(T)).Serialize(stringWriter,serialize);
            return stringWriter.ToString();
        }

        public static object DeserializeObject<T>(string serialized) => new XmlSerializer(typeof(T)).Deserialize(new StringReader(serialized));
        
    }
}

[schani]

@9ParsonsB Are all properties strings in SOAP/WSDL? What's the relationship between the two? Can one be mapped to the other? Is there an equivalent to classes in them?

[9ParsonsB]

No, I just didn't have an example at hand. I have updated SomeProperty to an int.
Edit: here is a list of XML (XSD) Types

WSDL is the definition of a SOAP service. SOAP is the actual message. Both are in XML.

Yes. <xs:complexType name="SomeRequestType"> is the Type whereas the actual element / request that contains the type is <xs:element name="SomeRequest" type="SomeRequestType">

The plan is to implement both (eventually) however I will probably start with SOAP and the required changes to add XML support (atleast to C#) to generated code and then move to WSDL

[9ParsonsB]

So there are quite a few parts to this issue:

1. Create XmlTypeBuilder to consume XSD (XML Schema) and convert to QuickType IR
2. 1. Extend CSharpRenderer to XmlCSharpRenderer and potentially SoapCSharpRenderer to create XML mapping as apose to JSON
2. Create XsdTypeBuilder to consume XSD (XML Schema) and convert to QuickType IR
3. Create WsdlTypeBuilder to take WSDL
4. Create XmlTypeBuilder to consume XSD
5. Create SoapTypeBuilder to consume SOAP

[schani]

You probably want to start with 2. It's the easiest of them all, and it will enable you to already get XML code by using an XML->JSON converter for input.

[schani]

@9ParsonsB What's the status on this? Do you need any help?

[9ParsonsB]

@schani XmlCSharpRenderer is still in progress. Not had much time to work on this lately. Will drop into slack when I get back into it.

[schani]

I'll close this. If you do end up finishing it, please submit a PR.

[IeuanWalker]

@9ParsonsB @schani
Could possibly use this library - https://github.com/abdolence/x2js or https://github.com/alabianca/xml-to-json

[ethindp]

Any update on this? I've been working with different XML data binding tools and the majority of them are (sadly) proprietary which is annoying. It would be great to have another tool that's free to try. My target language is, unfortunately, C++, but expat or Poco::XML (which is just a wrapper around expat) are good parsers for XML.