Printer Services Mail Archive: PS> FW: Web Services Interope

PS> FW: Web Services Interoperability guidelines - PSI WSDL Implicati ons

From: HALL,DAVID (HP-Vancouver,ex1) (dhall@hp.com)
Date: Tue Feb 18 2003 - 16:05:25 EST

  • Next message: McDonald, Ira: "RE: PS> FW: Web Services Interoperability guidelines - PSI WSDL I mplicati ons"

    > Hey All...
    >
    > In developing the WSDL for the PSI specification, we have been running
    > into many problems trying to implement a multi-parameter document-literal
    > encoding.
    >
    > What the below mentioned WSI interop guideline implies is that we should
    > NOT have multi-parameter messages. Rather we should have what I've seen
    > termed "Wrapped" document-literal.
    >
    > Essentially, in the WSDL we need to add an additional layer of "wrapping"
    > of the parameters. So for example, the CreatJob method would have a
    > CreateJob parameter that has all of our current parameters encapsulated
    > within it.
    >
    > I'll move ahead with this additional layer of encapsulation (wrapping) for
    > the PSI WSDL unless there is more discussion or comments.
    >
    > Comments?
    >
    > Dave
    >
    > -----Original Message-----
    > From: REVEL,DAN (HP-Vancouver,ex1)
    > Sent: Friday, February 14, 2003 3:47 PM
    > To: HALL,DAVID (HP-Vancouver,ex1)
    > Subject: Web Services Interoperability guidelines
    >
    > Dave,
    >
    > Here's a link to an Interoperabilty profile that we should consider when
    > constructing the WSDL for the PSI interface:
    >
    > http://www.ws-i.org/Profiles/Basic/2002-10/BasicProfile-1.0-WGD.htm
    >
    > Two things that caught my attention (and which will require changing the
    > current WSDL) are:
    >
    > R1000 When a MESSAGE contains a soap:Fault element, that element MUST NOT
    > have element children other than faultcode, faultstring, faultactor and
    > detail.
    > This seems to go against the inclusion of objects which you told me was
    > being proposed.
    >
    > and:
    >
    > R2201 If style="document" and use="literal" at the SOAP binding level, a
    > DESCRIPTION MUST have zero or one part in a wsdl:message element that
    > forms the soap:body.
    > R2204 If the style="document" and use="literal" at the SOAP binding level,
    > a DESCRIPTION MUST use the element attribute to define the single part in
    > a message.
    > This implies the wrapped behavior for the Axis toolkit.
    > From the Axis WSDL2Java reference guide:
    >
    > -W, --noWrapped
    > This turns off the special treatment of what is called "wrapped"
    > document/literal style operations. By default, WSDL2Java will recognize
    > the following conditions:
    > * If an input message has is a single part.
    > * The part is an element.
    > * The element has the same name as the operation
    > * The element's complex type has no attributes
    > When it sees this, WSDL2Java will 'unwrap' the top level element, and
    > treat each of the components of the element as arguments to the operation.
    > This type of WSDL is the default for Microsoft .NET web services, which
    > wrap up RPC style arguments in this top level schema element.
    >
    > Note the above description places a naming restriction on the single
    > element included in an input message, essentially the element name maps to
    > the operation/methed being called...
    >
    > Dan
    >



    This archive was generated by hypermail 2b29 : Tue Feb 18 2003 - 16:05:52 EST