Re: Nusoap 0.7.2: message definition changed when in doc/lit mode

OK, now I got it.

Those wrappers are generated automatically when in doc/lit mode.
Nice. I just have to rebuild my XSL.

Thanks Scott for well-documented code !!



--
Regards, Arek





> Hello,
>
>
> I see that nusoap v.0.7.2 changed the way messages are defined, when 
> working with "document/literal" mode. Messages don't contain parts, 
> which are function (call) parameters, but contain "parameters" part 
> instead.
> Could someone explain why it was done? And why only in "doc/lit" mode?
>
> Consider this method registration:
> $server->register(
>         'getDoc',
>         array('Domain' => 'xsd:string',
>         'FromDate' =>'xsd:string',
>         'ToDate' => 'xsd:string',
>         array('Return' => 'xsd:string'),
>         $NAMESPACE,false,'document','literal','Some description' );
>
>
> When looking at WSDL generated by nusoap-0.6.8, everything worked simply:
>
> Message definition for nusoap-0.6.8 is as follows (correct):
> <message name="getDocRequest">
>  <part name="Domain" type="xsd:string" />
>  <part name="FromDate" type="xsd:string" />
>  <part name="ToDate" type="xsd:string" />
> </message>
> <message name="getDocResponse">
>  <part name="Return" type="xsd:string" />
> </message>
>
>
> There is no Complex Type definition for getDocRequest or getDocResponse.
>
>
> Then compare it to WSDL generated by nusoap-0.7.2. There totally 
> different definition of message. You cannot reach so easily any element 
> of getDocRequest from my XSL stylesheets, as it was in nusoap-0.6.8:
> Message definition for nusoap-0.7.2 is as follows:
> <message name="getDocRequest">
>  <part name="parameters" element="tns:getDoc" />
> </message>
> <message name="getDocResponse">
>  <part name="parameters" element="tns:getDocResponse" />
> </message>
>
>
> Complex type definition for nusoap-0.7.2 is as follows:
>  <xsd:complexType name="getDocRequestType">
>   <xsd:all>
>    <xsd:element name="Domain" type="xsd:string"/>
>    <xsd:element name="FromDate" type="xsd:string"/>
>    <xsd:element name="ToDate" type="xsd:string"/>
>   </xsd:all>
>  </xsd:complexType>
>  <xsd:complexType name="getDocResponseType">
>   <xsd:all>
>    <xsd:element name="Return" type="xsd:string"/>
>   </xsd:all>
>  </xsd:complexType>
>
>  <xsd:element name="getDoc" type="tns:getDocRequestType"/>
>  <xsd:element name="getDocResponse" type="tns:getDocResponseType"/>

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf