If a datatype is an extension of another datatype, the wsclient only imports the elements of the derived datatype but not the elements of the parent datatype. Then the derived datatype must be manually updated by adding the elements of the parent datatype.

CommentFileSizeAuthor
#1 jobrequest.png47.21 KBblainelang

Comments

blainelang’s picture

blainelang commented
StatusFileSize
new jobrequest.png47.21 KB

@tuccio, I am looking at using this module as well and have hit the same issue. When the WSDL was imported in by wsclient, only the derived (extension) parms where defined and not the parent. Can you describe how you worked around this if you did.

Below is an extract from the WSDL and I've attached the image of the wsclient definition created.

<xs:complexType name="JobRequest">
  <xs:complexContent>
    <xs:extension base="tns:UserPassword">
      <xs:sequence>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="faxNumbers" nillable="true" type="tns:FaxNumber"/>
        <xs:element maxOccurs="unbounded" minOccurs="0" name="documents" nillable="true" type="tns:DocumentWithData"/>
        <xs:element minOccurs="0" name="options" type="tns:Options"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
tuccio’s picture

tuccio commented

I had to add manually the fields of the parent type. I found the parent type by looking at the

type="tns:XXX"

attribute and looking up the definition of the XXX type. This issue is surely to cause problems and should at least documented. What really helped me was to use dpm() from th Devel module and print out the returned object in each case.