Possible bug: WSDL 1.1 validation

[archenroot]

Hi,

I already posted potential validation bug regarding WSDL. I already reported bug at http://www.oxygenxml.com/forum/topic6395.html which seems to be fixed in version 13.

I explored another bug or feature to be implemented in new versions.

Situation is following. I have this piece of code in WSDL document:

Code: Select all

 <portType name="ZavodyVRoceBS">

    <operation name="getZavodyVRoce">

      <input message="bs:ZavodyVRoceReqMsg"/>

      <output message="bs:ZavodyVRoceRespMsg"/>

    </operation>

  </portType>

  

  <binding name="ZavodyVRoceBSSOAP11Binding" type="bs:ZavodyVRoceBS">

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

    <operation name="GetZavodyVRoce">

      <soap:operation style="document" soapAction="http://xmlns.lesycr.cz/BS/ZavodyVRoce/V1/GetZavodyVRoce"/>

      <input>

        <soap:body use="literal" parts="ZavodyVRoceListDM"/>

      </input>

      <output>

        <soap:body use="literal" parts="ZavodyVRoceRespDM"/>

      </output>

    </operation>

  </binding>

It is OK in the first look, but there is "Case object name error":

Code: Select all

  <portType name="ZavodyVRoceBS">

    <operation name="getZavodyVRoce"> starts with small letter



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

    <operation name="GetZavodyVRoce"> but here it starts with big one

Both names schould be same in WSDL file as soon as abstract definition in portType area becomes concrete at binding area, so these operations are referencing same object.

Best regards,

Ladislav

[Radu]

Hi Ladislav,

You are right the validation reports problems when the operation in the binding has a name which is not found in the WSDL but if the name of the operation only has a small capitalization problem the validation seems to succeed.

The WSDL specification states:

An operation element within a binding specifies binding information for the operation with the same name within the binding's portType.

We'll try to modify the validation to report this kind of problem and update this forum post when this happens.

Regards,
Radu

[Radu]

Hi,

Oxygen 13.2 which will appear at the beginning of the next year will correctly report such capitalization problems in the WSDL validation.

Regards,
Radu