WS-I compliance

["Enrique Othon" <Enrique@wiznet.com>]

The web services specification states that WS-I Basic Profile 1.1
compliance is required but the web services messaging profile definition
wsdl is not compliant.

 

Specifically it fails test assertion BP2119.

 

Assertion Description: 
If it does not specify the parts attribute on a soapbind:body element,
the corresponding abstract wsdl:message defines zero or one wsdl:part. 

Failure Message: 
A document-literal binding which does not specify the parts attribute,
has more than one wsdl:part in the associated wsdl:message element. 

Failure Detail Description: 
Defective wsdl:binding element. 

For example in the wsdl:

 

<message name="ServeFilingRequest">

        <part name="CoreFilingMessage"
element="core:CoreFilingMessage"/>

        <part name="CaseTypeSpecificMessage"
element="casetype:CaseTypeSpecificMessage"/>

        <part name="CourtSpecificMessage"
element="court:CourtSpecificMessage"/>

    </message>

 

<binding name="ServiceMDEPortSOAPBinding" type="wsmp:ServiceMDEPort">

        <soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>

        <operation name="ServeFiling">

            <soap:operation soapAction=""/>

            <input name="ServeFilingRequest"><soap:body
use="literal"/></input>

            <output name="ServeFilingResponse"><soap:body
use="literal"/></output>

        </operation>

    </binding>

 

The soap:body element for the input doesn't specify the parts attribute
so the associated message element should have 1 or zero parts.