WSDL/SOAP CORBA Interworking Avatar
  1. OMG Specification

WSDL/SOAP CORBA Interworking — Closed Issues

  • Acronym: WSDL2C
  • Issues Count: 22
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
WSDL2C-22 Section: 1.2.11 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-21 Example WSDL Does not verify WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-20 CORBA Source Annotation Namespace in schema WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-17 Section 1.2.8.2 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-18 Section 1.2.8.5 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-19 CORBA Object Reference Schema WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-16 there should NOT be a ¡°_target¡± element defined WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-14 element hierarchy is not valid WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-15 The section "Typedef" needs an example with a no basic type WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-13 Multiple target namespaces in Wsdl File WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-12 Document/Literal style/use WSDL WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-11 reference to schema elements WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-10 new clarfication issue for the WSDL to CORBA FTF WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-9 Issue: wsdlCorba09 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-8 Issue: wsdlCorba08 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-7 Issue: wsdlCorba07 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-6 Issue: wsdlCorba06 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-5 Issue: wsdlCorba05 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-4 Issue: wsdlCorba04 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-3 Issue: wsdlCorba03 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-1 Issue: wsdlCorba01 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed
WSDL2C-2 Issue: wsdlCorba02 WSDL2C 1.0b1 WSDL2C 1.0 Resolved closed

Issues Descriptions

Section: 1.2.11

  • Key: WSDL2C-22
  • Legacy Issue Number: 8755
  • Status: closed  
  • Source: cpan ( Francois Perrad)
  • Summary:

    The unknown type "xsd:url" must be replaced by "xsd:anyURI" in corba.wsdl. There are 2 occurences : <element name="url" ... <element name="definition" ...

  • Reported: WSDL2C 1.0b1 — Tue, 3 May 2005 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    replace "xsd:url" with "xsd:anyURI" in both occurrences

  • Updated: Sat, 7 Mar 2015 04:08 GMT

Example WSDL Does not verify

  • Key: WSDL2C-21
  • Legacy Issue Number: 7835
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Corba IDL to WSDL interworking: ptc/03-11-02

    Section 1.2.8 and 1.2.9 have several example wsdl descriptions.

    However, these are not in the proper format for a wsdl description.

    They should be editorially fixed in the Document, and made

    availalbe as informative files.

    Solution Proposed by Submitter:

    In Section 1.2.8 and 1.2.9 fix the wsdl descriptions to validate with the wsdl schema, and make them available as files.

    The RTF chair will make these files available in time for the vote on this issue.

  • Reported: WSDL2C 1.0b1 — Mon, 4 Oct 2004 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    : Close with accepting revised text below

  • Updated: Sat, 7 Mar 2015 04:08 GMT

CORBA Source Annotation Namespace in schema

  • Key: WSDL2C-20
  • Legacy Issue Number: 7834
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Corba IDL to WSDL interworking: ptc/03-11-02

    Section 1.2.3: Identifying the Source IDL

    The text states that the annotation elements are in the CORBA namespace.

    However both schema have the wrong targetNamespace.

    The erroneous schema namespace information should be deleted. Put all the corba namespace type and element definitions in a single normative schema section and file.

    Solution Proposed by Submitter:

    In Section 1.2.3:

    On pages 1-3 and 1-4

    Delete the first four lines of each schema:

    <?xml version="1.0" encoding="UTF-8"?>

    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"

    targetNamespace="http://www.omg.org/IDL-MAPPED"

    elementFormDefault="qualified" attributeFormDefault="unqualified">

    and delete the final line of each schema:

    </xsd:schema>

    Add the following new normative schema for the CORBA namespace, gathering all the type and element definitions spread throughout the document (the schema for objectReference, from issue xxxx, is fixed in this new schema):

    <?xml version="1.0" encoding="utf-8"?>

    <!--

    WSDL for IDL to WSDL CORBA Namespace

    Name: corba.wsdl

    -->

    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:corba="http://www.omg.org/IDL-WSDL/1.0/" targetNamespace="http://www.omg.org/IDL-WSDL/1.0/" name="corba">

    <types>

    <xsd:schema targetNamespace="http://www.omg.org/IDL-WSDL/1.0/">

    <xsd:element name="SourceIDL" >

    <xsd:annotation>

    <xsd:documentation>IDL/WSDL Mapping Info</xsd:documentation>

    </xsd:annotation>

    <xsd:complexType>

    <xsd:sequence>

    <xsd:element name="source" type="xsd:string" minOccurs="1" maxOccurs="1"/>

    <xsd:element name="version" type="xsd:string" minOccurs="1" maxOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

    </xsd:element>

    <xsd:element name="SourceRepositoryID" >

    <xsd:annotation>

    <xsd:documentation>IDL Mapped Repository ID </xsd:documentation>

    </xsd:annotation>

    <xsd:complexType>

    <xsd:sequence>

    <xsd:element name="repositoryID" type="xsd:string" minOccurs="1" maxOccurs="1"/>

    <xsd:element name="version" type="xsd:string" minOccurs="1" maxOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

    </xsd:element>

    <xsd:complexType name="ObjectReference">

    <xsd:sequence>

    <xsd:element name="url" type="xsd:url" minOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

    <xsd:complexType name="CORBA.TypeCode">

    <xsd:sequence>

    <xsd:element name="definition" type="xsd:url" maxOccurs="1" minOccurs="1"/>

    <xsd:element name="typename" type="xsd:string" maxOccurs="1" minOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

    <xsd:complexType name="CORBA.Any">

    <xsd:sequence>

    <xsd:element name="type" type="corba:CORBA.TypeCode" maxOccurs="1" minOccurs="1"/>

    <xsd:element name="value" type="xsd:anyType" maxOccurs="1" minOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

    <xsd:simpleType name="CORBA.completion_status">

    <xsd:restriction base="xsd:string">

    <xsd:enumeration value="COMPLETED_YES"/>

    <xsd:enumeration value="COMPLETED_NO"/>

    <xsd:enumeration value="COMPLETED_MAYBE"/>

    </xsd:restriction>

    </xsd:simpleType>

    <xsd:complexType name="CORBA.SystemException">

    <xsd:sequence>

    <xsd:element name="minor" type="xsd:unsignedInt" maxOccurs="1" minOccurs="1"/>

    <xsd:element name="completion_status" type="corba:CORBA.completion_status" maxOccurs="1" minOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

    </xsd:schema>

    </types>

    <message name="CORBA.SystemExceptionMessage">

    <part name="_return" type="corba:CORBA.SystemException"/>

    </message>

    </definitions>

  • Reported: WSDL2C 1.0b1 — Mon, 4 Oct 2004 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Close with accepting solution proposed by submitter

  • Updated: Sat, 7 Mar 2015 04:08 GMT

Section 1.2.8.2

  • Key: WSDL2C-17
  • Legacy Issue Number: 7743
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Section 1.2.8.2
    In the example(Page 1-22, top), "readonly" attribute is mapped as follows:
    <operation name="_get_longAttr" >
    <output message="tns:MyAttrs._get_longAttrResponse"/>
    <fault message=¡±tns:CORBA.SystemException¡±/>
    </operation>

    But in most of the SOAP specification implementations(Axis, .NET 1.1 etc.), the format like this means the

    operation is a 'notify' operation.

    Proposed solution: Maybe we should map as follows:

    <message name=¡±longAttrRequest¡±>
    </message>

    <operation name=¡±_get_longAttr¡±>
    <input message=¡±tns:longAttrRequest¡± />
    <output message=¡±tns:MyAttrs._get_longAttrResponse¡±/>
    <fault message=¡°tns:CORBA.SystemException¡±>
    </operation>

  • Reported: WSDL2C 1.0b1 — Mon, 13 Sep 2004 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Close as Duplicate of Issue 6996

  • Updated: Sat, 7 Mar 2015 04:08 GMT

Section 1.2.8.5

  • Key: WSDL2C-18
  • Legacy Issue Number: 7744
  • Status: closed  
  • Source: Anonymous
  • Summary:

    In the example:
    <portType name="Example.SomeInterface">
    <operation name="bar" parameterOrder="_target pi">
    <input message="tns:Example.SomeInterface.bar"/>
    <output message="tns:Example.SomeInterface.barResponse"/>
    <fault message="_exception.Example.BadRecord"/>
    <fault message="_exception.Example.UnknownError"/>
    <fault message=¡±tns:CORBA.SystemException¡±/>
    </operation>
    </portType>
    Most of the WSDL2java tool will use element'name' as a parameter's name. So, on receiving the WSDL as above (page
    1-25), most WSDL2java tool will report an error in process for mapping WSDL to java.

    Proposed solution: Maybe we should add a 'name' attribute in the fault element. For example, consider the
    following IDL:
    module Example{
    exception BadRecord

    { String why; }

    ;
    Interface SomeInterface

    { Long bar(in float pi) raises(BadRecord),UnknownError }

    }
    It should be mapped to:
    <portType name="example.SomeInterface">
    <operation name="bar" >
    <input message="tns:Example.SomeInterface.bar" />
    <output message="tns:Example.SomeInterface.barResonse"/>
    <fault message="_exception.Wxample.BadRecord" name="badRecord"/>
    <fault message="_exception.Example.UnknownError" name="error"/>
    <fault message="tns:CORBA.SystemException" name="systemError"/>
    </operation>
    </portType>

  • Reported: WSDL2C 1.0b1 — Mon, 13 Sep 2004 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    : Accept proposed change from source

  • Updated: Sat, 7 Mar 2015 04:08 GMT

CORBA Object Reference Schema

  • Key: WSDL2C-19
  • Legacy Issue Number: 7832
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Corba IDL to WSDL interworking: ptc/03-11-02

    Section 1.2.5: Object References

    The text states that the object reference maps to a sequence of URLs.

    However the schema has a maxOccurs=1 for the element.

    Solution Proposed by Submitter:

    In Section 1.2.5 change:

    <xsd:complexType name="ObjectReference">

    <xsd:sequence>

    <xsd:element

    name="url" type="xsd:url"

    maxOccurs="1" minOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

    to

    <xsd:complexType name="ObjectReference">

    <xsd:sequence>

    <xsd:element

    name="url" type="xsd:url"

    minOccurs="1"/>

    </xsd:sequence>

    </xsd:complexType>

  • Reported: WSDL2C 1.0b1 — Mon, 4 Oct 2004 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Close with accepting solution proposed by submitter

  • Updated: Sat, 7 Mar 2015 04:08 GMT

there should NOT be a ¡°_target¡± element defined

  • Key: WSDL2C-16
  • Legacy Issue Number: 6638
  • Status: closed  
  • Source: Anonymous
  • Summary:

    In the example, bar operation defined in SomeInterface are mapped as the following:

    <message name="Example.SomeInterface.bar" >

    <part name="_target" type="CORBA:Reference"/>

    <part name="pi" type="xsd:float"/>

    </message>

    But according to the mapping rule in Section 1.2.8.2, there should NOT be a ¡°_target¡± element defined in the message. Whats more, CORBA::Reference has not been defined in the specification.

    Proposed solution: Please make sure that ¡°_target¡± is required or optional.

  • Reported: WSDL2C 1.0b1 — Tue, 25 Nov 2003 05:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    see above

  • Updated: Sat, 7 Mar 2015 04:08 GMT

element hierarchy is not valid

  • Key: WSDL2C-14
  • Legacy Issue Number: 6631
  • Status: closed  
  • Source: cpan ( Francois Perrad)
  • Summary:

    In the WS-I mapping of IDL sequence, the following element hierarchy is not valid : complexType / complexContent / sequence / element ('sequence' MUST NOT be a child of a 'complexContent')

    A valid hierarchy is : complexType / sequence / element

    Same issue for arrays in section 1.2.7.6.

  • Reported: WSDL2C 1.0b1 — Tue, 18 Nov 2003 05:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Remove the erroneous "complexContent" level from the hierarchy for both section 1.2.7.5 and 1.2.7.6.

  • Updated: Sat, 7 Mar 2015 04:08 GMT

The section "Typedef" needs an example with a no basic type

  • Key: WSDL2C-15
  • Legacy Issue Number: 6634
  • Status: closed  
  • Source: cpan ( Francois Perrad)
  • Summary:

    The section "Typedef" needs an example with a no basic type, like following :

    // IDL struct S

    { long dummy; }

    ; typedef S S_t;

    // XSD <xsd:complexType name="S"> <xsd:sequence> <xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1" /> </xsd:sequence> </xsd:complexType>

    <xsd:complexType name="S_t"> <xsd:complexContent> <xsd:restriction base="tns:S"> <xsd:sequence> <xsd:element name="dummy" type="xsd:int" maxOccurs="1" minOccurs="1" /> </xsd:sequence> </xsd:restriction> </xsd:complexContent> </xsd:complexType>

  • Reported: WSDL2C 1.0b1 — Thu, 20 Nov 2003 05:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Add the proposed example to the revision text

  • Updated: Sat, 7 Mar 2015 04:08 GMT

Multiple target namespaces in Wsdl File

  • Key: WSDL2C-13
  • Legacy Issue Number: 6289
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    A WSDL description can contain multiple namespaces, including:

    • the description can have its own target namespace
    • the description can use wsdl: import to import a wsdl namespace
    • zero or moer schema in the types section has a target namespace (which is allowed, by WS-I profile, to be same as target namespace for the wsdl description
    • The schema in a types section can use xsd:import to import multiple namespaces.

    The current wsdl to corba inteworking spec only discusses the first namespace in the above list.
    The specification needs to clarify that each of the multiple namespaces in the wsdl description needs
    to be mapped to its own IDL module (using the same naming algorithm as currently specified for the wsdl target namespace)

    Propose solution:

    Amend the specification to map each namespace in the wsdl description to its own IDL module.

  • Reported: WSDL2C 1.0b1 — Mon, 6 Oct 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Close with new text mapping each target namespace to its own IDL module

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Document/Literal style/use WSDL

  • Key: WSDL2C-12
  • Legacy Issue Number: 6282
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    With Document/Literal style/use WSDL, the message parts refer to global element declarations.

    In XML schema language, these global elements definitions are allowed to be anonymous. In
    such a case there is no named type for the corresponding corba operation parameter.

    Proposed solution:

    When required, the translator must generate a type name by adding the prefix "T_" to the name
    of the element. The OMG IDL for the inteface must generate a typedef using this generated
    typename

  • Reported: WSDL2C 1.0b1 — Wed, 1 Oct 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Close with the addition of prefix when required for anonymous types

  • Updated: Fri, 6 Mar 2015 20:51 GMT

reference to schema elements

  • Key: WSDL2C-11
  • Legacy Issue Number: 6274
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    I was wondering if we have a problem in the spec regarding WSDL which has parts defined
    with reference to schema elements, rather than shema types.
    In Document-literal, the parts are defined in wsdl with reference to globally defined element defs.

    Now what happens to our mapping when these globally defiined elements have anonymous types
    (i.e., the element is defined inline as a complex type wihout a type name)?

    Do we have a problem in this case?

  • Reported: WSDL2C 1.0b1 — Fri, 26 Sep 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Close as Duplicate of Issue 6282

  • Updated: Fri, 6 Mar 2015 20:51 GMT

new clarfication issue for the WSDL to CORBA FTF

  • Key: WSDL2C-10
  • Legacy Issue Number: 6273
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Here is a new clarfication issue for the WSDL to CORBA FTF.

    The subject of the WSDL/SOAP to CORBA Interworking Specification includes two subcases for a CORBA client accessing a WSDL/SOAP server instance..

    One subcase (mandatory for conformance) is for a service originally defined in WSDL, using the WSDL to IDL mapping defined in this specification.

    The second subcase (optional for conformance) is for a CORBA client accessing a WSDL service, which is itself a transated spec originally defined in IDL, which has incorporated a source indication in the translated WSDL file. This mechanism, to avoid round trip translation, is specified in the separate IDL to WSDL specification.

    Implementation of the second sub case needs to be clarified, by the FTF including additional descriptive text, as an optional conformance point for WSDL/SOAP to CORBA Interworking.

  • Reported: WSDL2C 1.0b1 — Mon, 22 Sep 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba09

  • Key: WSDL2C-9
  • Legacy Issue Number: 6036
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Clause 6.5 states the clause is preliminary.

    Resolution proposed by Originator:

    After FTF resolves all the complex type issues, delete the sentence “This section is preliminary”.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    editorial

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba08

  • Key: WSDL2C-8
  • Legacy Issue Number: 6035
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Description of Issue:

    Clause 6.4.3 has a generic mapping of restricted XML types to wstring. It would provide more information to the receiver if there was a different IDL typedef of wstring for each restricted XML type in the list.

    Resolution proposed by Originator:

    FTF should provide a separate typedef of wstring for mapping each of the generic types listed in clause 6.4.3.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Close with addition of separate typdef for each generic type in a special IDL module

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba07

  • Key: WSDL2C-7
  • Legacy Issue Number: 6034
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Description of Issue:

    Clause 6.5 has no mapping for xml attributes of complex types. They are used a lot in WSDL document definitions.

    Resolution proposed by Originator:

    FTF should provide mapping for xml attributes of complexType. Originator suggests mapping each xml attribute as an additional elements within the IDL struct corresponding to the complex type.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Treat attributes as extra members, added to the mapped IDL struct for the complex type

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba06

  • Key: WSDL2C-6
  • Legacy Issue Number: 6033
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Description of Issue:

    Clause 6.5 has no mapping for elements of complex types with maxOccurs>1. This is used a lot in WSDL document definitions.

    Resolution proposed by Originator:

    FTF should provide mapping for elements in ComplexContent which have maxOccurs>1. Originator suggests mapping to an IDL sequence element within the struct corresponding to the complex type.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Add new subsection to cover mapping elements with cardinality

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba05

  • Key: WSDL2C-5
  • Legacy Issue Number: 6032
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Description of Issue:

    Clause 6.5 has no mapping for elements of complex types with minOccurs=0. This is used a lot in WSDL document definitions.

    Resolution proposed by Originator:

    FTF should provide mapping for elements with minOccurs=0 within a complex type. Originator suggests mapping to an IDL sequence element within the struct corresponding to the complex type.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba04

  • Key: WSDL2C-4
  • Legacy Issue Number: 6031
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Description of Issue:

    6.5 is missing subsection for mapping xsd:all, however it is mapped the same as xsd:sequence in the example section.

    Resolution proposed by Originator:

    FTF should add a new subsection to specify the mapping for ComplexContent “all”. The mapping should be the same as for sequence.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    map all similar to sequence

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba03

  • Key: WSDL2C-3
  • Legacy Issue Number: 6030
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Description of Issue:

    Clause 5, resulting from the new Specification Template, needs to be completed.

    Resolution proposed by Originator:

    FTF needs to provide text for symbols and abbreviations clause.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Add appropriate abbreviations text

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba01

  • Key: WSDL2C-1
  • Legacy Issue Number: 6028
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Clause 3, resulting from the new Specification Template, needs to be completed.

    Resolution proposed by Originator:

    FTF needs to provide complete set of references

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    FTF needs to provide complete set of references

  • Updated: Fri, 6 Mar 2015 20:51 GMT

Issue: wsdlCorba02

  • Key: WSDL2C-2
  • Legacy Issue Number: 6029
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Description of Issue:

    Clause 4, resulting from the new Specification Template, needs to be completed.

    Resolution proposed by Originator:

    FTF need to provide text for terminology clause.

  • Reported: WSDL2C 1.0b1 — Fri, 1 Aug 2003 04:00 GMT
  • Disposition: Resolved — WSDL2C 1.0
  • Disposition Summary:

    Add a terminology clause

  • Updated: Fri, 6 Mar 2015 20:51 GMT