Issues for CORBA/WSDL Revision Task Force

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Jira Issues

Issue 8991: Section: 1.2.7.6 Jira Issue C2WSDL12-2
Issue 8992: Section: 1.2.7.6 Jira Issue C2WSDL12-3
Issue 8994: Section: 1.2.7.6 page 1-14 Jira Issue C2WSDL12-4
Issue 8995: Section: 1.2.7.6 Multi-dimensional arrays in IDL Jira Issue C2WSDL12-5
Issue 9600: Section: 1.2.7.5 and 1.2.7.6 (CorbaToWsdl) Jira Issue C2WSDL12-6
Issue 9601: Section: 1.2.11 (CorbaToWsdl) Jira Issue C2WSDL12-7
Issue 9602: Section: 1.2.x (CorbaToWsdl) Jira Issue C2WSDL12-8
Issue 9603: Section: 1.2.x (CorbaToWsdl) Jira Issue C2WSDL12-11
Issue 9604: Section: 1.2.7.6 (CorbaToWsdl) Jira Issue C2WSDL12-9
Issue 9611: Section: 1.2.6.1 (CorbaToWsdl) Jira Issue C2WSDL12-10
Issue 11687: Section: 4.1.9 SOAP Binding Jira Issue C2WSDL12-1

Issue 8991: Section: 1.2.7.6 (corbawsdl-rtf)

In section 1.2.7.6 page 1-13, the implicit IDL declaration of the following struct S { long field[10]; }; generates a complex type _SE_S.field_ArrayOfint for the soap-encoded ::S::field. The complex type _SE_S (corresponding to soap-encoded struct S) refers to field with type S._SE_field_ArrayOfint. There is no schema type _S._SE_field_ArrayOfint. Resolution: The soap-encoded name of S.field should be _S._SE_field_ArrayOfint as shown in the following excerpt. <xsd:complexType name="S._SE_field_ArrayOfint"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="10" maxOccurs="10"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_S"> <xsd:sequence> <xsd:element name="field" type="S._SE_field_ArrayOfint" minOccurs="1" maxOccurs="1" </xsd:sequence> </xsd:complexType>   

Agreed to fix example text, Struct S is a type which must have _SE_ prefix for soap encoded version of mapping

The specification in section 1.2.7.6 page 1-14 gives the following IDL as example for multi-dimensional arrays typedef long matrix[5][3] What the above array is mapped to is semantically equivalent to matrix[3][5]. Proposed resolution: What we think should be the correct order for the expanded multi-dimenstional array is shown in the following XSD schema: <xsd:complexType name="_SE_ArrayOfint_matrix_3"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" axOccurs="3"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_matrix"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="_SE_matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="_SE_matrix_3[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="ArrayOfint_matrix_3"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="matrix"> <xsd:sequence> <xsd:element name="item" type="matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> </xsd:complexType>   

: In the example typedef long matrix[5][3]; matrix is treated as an array of size 3, where each element is an array of integers of size 5.  The indexes progress from inside to outside.  This is different than CDR encoding, but the difference is not a problem.  Resolution: Although there is a difference from CDR ordering, there is no problem with the mapping order.  Changing to the same order as CDR is beyond the scope of an RTF..  

The specification in section 1.2.7.6 page 1-14 gives the following IDL as example for multi-dimensional arrays typedef long matrix[5][3] What the above array is mapped to is semantically equivalent to matrix[3][5]. Proposed resolution: What we think should be the correct order for the expanded multi-dimenstional array is shown in the following XSD schema: <xsd:complexType name="_SE_ArrayOfint_matrix_3"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_matrix"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="_SE_matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="_SE_matrix_3[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="ArrayOfint_matrix_3"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="matrix"> <xsd:sequence> <xsd:element name="item" type="matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> </xsd:complexType>     

Multi-dimensional arrays in IDL are required to be mapped to intermediate types for each of the sub-arrays. The naming scheme used by the specification can lead to name collision. Referring to section 1.2.7.6 page 1-14, an IDL with the following declaration typedef long matrix [5][3]; maps to complex types as below: <xsd:complexType name="_SE_ArrayOfint"> ... </xsd:complexType> <xsd:complexType name="_SE_matrix"> ... </xsd:complexType> <xsd:complexType name="ArrayOfint"> ... </xsd:complexType> <xsd:complexType name="matrix"> ... </xsd:complexType> However, if you have another type in the above IDL typedef long anotherMatrix[5][3]; This will also map to complex types with names _SE_ArrayOfint, _SE_anotherMatrix, ArrayOfint, anotherMatrix leading to name collision between XML schema types. Same goes for more than two-dimensional arrays. Proposed resolution: To have name collision-free types, an approach can be to include the name and size of that particular array. For example, the above IDL will produce the following schema types. <xsd:complexType name="_SE_ArrayOfint_matrix_3"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:int[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="_SE_matrix"> <xsd:complexContent> <xsd:restriction base="SOAP-ENC:Array"> <xsd:sequence> <xsd:element name="item" type="_SE_matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="_SE_matrix_3[]"/> </xsd:restriction> </xsd:complexContents> </xsd:complexType> <xsd:complexType name="ArrayOfint_matrix_3"> <xsd:sequence> <xsd:element name="item" type="xsd:int" minOccurs="3" maxOccurs="3"/> </xsd:sequence> </xsd:complexType> <xsd:complexType name="matrix"> <xsd:sequence> <xsd:element name="item" type="matrix_3" minOccurs="5" maxOccurs="5"/> </xsd:sequence> </xsd:complexType>     

RTF should make minimal fixes to problems found.  RTF should not change the mapped identifiers when a collision does not occur.

In Corba to WSDL/SOAP Interworking Spec:  In section 1.2.7.5 and 1.2.7.6, the examples of soap encoded array   types have the _SE_ prefix after the module identifier.  The "_SE"   prefix is supposed to be at the beginning of the mapped type name.    Proposed Resolution: fix the examples to change "Example._SE_" to "_SE_Example."  Revised Text:   In 1.2.7.5 three occurances:  <xsd:complexType name="Example._SE_longSeq">    <xsd:complexType name="Example._SE_strSeq">    <xsd.complexType name="Example._SE_structSeq">    In 1.2.7.6 one occurance:    <xsd:complexType name="Example._SE_arrayLong" >    Change:  "  "Example._SE_"  To  "_SE_Example."    

The module prefex should be treated the same as if it were an xml namespace prefix.    The decoration with soap encoding labels should occur in the type name before the module prefixes are attached,  exactly as shown in the examples..  

In Corba to WSDL/SOAP Interworking Spec:  In section 1.2.11, the CORBA namespace file is missing the production for _VALREF.    Proposed Resolution: Add the production for _VALREF to the corba.wsdl file  Revised Text:   Add the following production, from  1.2.7.10, to the corba.wsdl file in 1.2.11:  "     <xsd:complexType name="_VALREF">        <xsd:attribute name="ref" type="xsd:IDREF" use="optional" />              <!-- empty attribute used for null semantics, i.e., value graph end nodes -->     </xsd:complexType>  "    

In Corba to WSDL/SOAP Interworking Spec:  In section 1.2.x  there are several typographical errors in the  XML schema productions for the examples.  Several schema productions  could not validate as written.    Proposed Resolution: correct the typographical errors to allow the xml schema productions to validate.  Revised Text:   Change G1: to make specification text consistent with the validated machine readable example files, in            https://www.omg.org/cgi-bin/doc?ptc/04-10-12   ---------------------------------  In 1.2.1.1 change the namespace prefixes:  "wsdl" to "w"  and  "SOAP-ENC" to "soapenc"    Throughout the document, wherever soap encoding array is used:  Change:  "  SOAP-ENC  "  To:  "  soapenc  "  And:  Change:  "  wsdl:  "  To:  "  w:  "  And  Change:  "[]"  To:  ""  --------------------------------end change G1    In 1.2.6.1, apply change G1  And:  Change:  "  </xsd.complexType>  "  To:  "        </xsd:complexType>   "    In 1.2.7.1 Change:  "<simpleType" to "<xsd:simpleType" and "</simpleType" to "</xsd:simpleType"    In 1.2.7.3 Change:       Example.Number>  to:       Example.Number">  And change:      Example.OtherNumber>  To:      Example.OtherNumber">  And Change:  "      xsd:sequence>          xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1" />      /xsd:sequence>  "  To:  "        <xsd:sequence>           <xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1"/>        </xsd:sequence>  "  And change:  "      xsd:complexContent>          xsd:restriction base="tns:S">              xsd:sequence>                  xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1" />   "  To:  "        <xsd:complexContent>           <xsd:restriction base="tns:S">              <xsd:sequence>                 <xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1"/>  "    In 1.2.7.5 apply change G1:    In 1.2.7.6    apply change G1 to arrayLong example:    apply change G1 to struct S example    apply change G1 to matrix example    In 1.2.7.10 change:  <complexType to:  <xsd:complexType    And change:  <xsd:attribute> to:  <xsd:attribute   

: In Corba to WSDL/SOAP Interworking Spec:  In section 1.2.7.6, the IDL identifier "S" at top level has already been used for another example.    Also have to make editorial corrections to allow schema to validate.    Proposed Resolution: change second use of "S" To "T", and apply resolution to issue 8991  Revised Text:   In  1.2.7.6  change the following explicitly listed lines: (where "�" implies one or more intervening lines)  "  struct S {  �  <xsd:complexType name="_SE_S.field_ArrayOfint">  �  <xsd:complexType name="_SE_S">  �  <xsd:element name="field" type="S._SE_field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>  �  <xsd:complexType name="S.field_ArrayOfint">  �  <xsd:complexType name="S">    <xsd:element name="field" type="S.field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>  �  "  To: (this change also incorporates resolution to Issue 8991)   "  struct T {  �  <xsd:complexType name="_SE_T.field_ArrayOfint">  �  <xsd:complexType name="_SE_T">  �  <xsd:element name="field" type="_SE_T.field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>  �  <xsd:complexType name="T.field_ArrayOfint">  �  <xsd:complexType name="T">  �  <xsd:element name="field" type="T.field_ArrayOfint" nillable="true" maxOccurs="1" minOccurs="1"/>  �  "  

In Corba to WSDL/SOAP Interworking Spec:  In section 1.2.6.1 a soap encoded form for the sequence is used, however the type identifier does not have the _SE_ suffix.    Proposed Resolution: fix the example to be a WS-I BP compliant sequence mapping only.  Revised Text:  In 1.2.6.1, change:  "  which maps to:  "  To:  "  which maps to (only the WS-I BP compliant version is shown for simplicity):  "  And, remove the following explicit lines (where � denotes intervening lines to be retained):  "      <xsd:complexContent>          <xsd:restriction base="SOAP-ENC:Array">  �              <xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:string[]"/>          </xsd:restriction>      </xsd:complexContent>  "  

The binding of CORBA System exception is not complete , regarding WSDL 1.1 (see http://www.w3.org/TR/wsdl#_soap:fault Each occurrence of : <fault name="CORBA.SystemException"/> must be replaced by : <fault name="CORBA.SystemException"/> <soap:fault name="CORBA.SystemException" use="literal"/> </fault> More details on http://rt.cpan.org/Ticket/Display.html?id=30893