WSDL file produces error #37

Activity

1. Bouke commented on Nov 12, 2017

   

   Bouke

   on Nov 12, 2017

   Last edited by Bouke

   Owner

   More actions

   There are a few types defined within a XSD https://www.onvif.org/ver10/schema/onvif.xsd which is included by the WSDL. The first two I ran into are these;

   Currently Lark doesn't support the ref attribute on an element:

       <xs:complexType name="AttachmentData">
           <xs:sequence>
               <xs:element ref="xop:Include"/>
           </xs:sequence>
           <xs:attribute ref="xmime:contentType" use="optional"/>
       </xs:complexType>

   Currently Lark doesn't support a complexType with simpleContent:

       <xs:complexType name="CertificateUsage">
           <xs:simpleContent>
               <xs:extension base="xs:string">
                   <xs:attribute name="Critical" type="xs:boolean" use="required"></xs:attribute>
               </xs:extension>
           </xs:simpleContent>
       </xs:complexType>

   Currently Lark doesn't support a complexType with a choice value type:

   <xs:complexType name="ColorOptions">
       <xs:annotation>...</xs:annotation>
       <xs:choice>
           <xs:element name="ColorList" type="tt:Color" maxOccurs="unbounded">
               <xs:annotation>
                   <xs:documentation>List the supported color.</xs:documentation>
               </xs:annotation>
           </xs:element>
           <xs:element name="ColorspaceRange" type="tt:ColorspaceRange" maxOccurs="unbounded">
               <xs:annotation>
                   <xs:documentation>Define the rang of color supported.</xs:documentation>
               </xs:annotation>
           </xs:element>
       </xs:choice>
       <xs:anyAttribute processContents="lax"></xs:anyAttribute>
   </xs:complexType>

   Ideally Lark would support these message types. Or maybe skip the parts of the WSDL/XSD it cannot deal with. I've created a branch feature/more-complex and committed three failing tests for each of the types listed above. I don't know if/when I might have time to further look at this, but at least it's recorded somewhere now.

   However at this moment you'd have to work around the limitations of Lark to get the client generated. It shouldn't be too hard by running lark-generate-client from Xcode and put in a small workaround at those spots it's throwing a error.