cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gregor Weiske <gwei...@progress.com>
Subject WSDL validator - bug?
Date Mon, 10 May 2010 21:45:25 GMT
Hello,

If I understand http://www.w3.org/TR/wsdl#_soap:body specifically ...
<definitions .... >
    <binding .... >
        <operation .... >
           <input>
               <soap:body parts="nmtokens"? use="literal|encoded"?
                          encodingStyle="uri-list"? namespace="uri"?>
           </input>
           <output>
               <soap:body parts="nmtokens"? use="literal|encoded"?
                          encodingStyle="uri-list"? namespace="uri"?>
           </output>
        </operation>
    </binding>
</definitions>

... correctly, then e.g. ...

  <wsdl:binding name...
    <soap:binding ...>
    <wsdl:operation ...>
      <soap:operation style="document"/>
      <wsdl:input>
        <soap:body use="literal" parts="part1 part2 part3"/>
      </wsdl:input>
      <wsdl:output>
       ...
... should be valid WSDL. However, the apache-cxf-2.2.6\bin\wsdlvalidator tells me:

WSDLValidator Error : WSI-BP-1.0 R2201 violation: Operation 'MultiPartStringInt' more than
one part bound to body

If I change the WSDL fragment to the following, there are no complaints from the validator.
  <wsdl:binding name...
    <soap:binding ...>
    <wsdl:operation ...>
      <soap:operation style="document"/>
      <wsdl:input>
        <soap:body use="literal" parts="part1"/>
        <soap:body use="literal" parts="part2"/>
        <soap:body use="literal" parts="part3"/>
      </wsdl:input>
      <wsdl:output>

Bug?

Thanks

Gregor

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message