CORBA to WSDL/SOAP Interworking Avatar
  1. OMG Specification

CORBA to WSDL/SOAP Interworking — Closed Issues

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

Issues Descriptions

CORBA to WSDL/SOAP: example for attributes mapping

  • Legacy Issue Number: 6996
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Section 1.2.8.2
    In the example for attributes mapping.
    The get accessor maps to an operation with only an output message. It seems like a notification operation according to WSDL specification. But the semantics of attribute accessors should be request-response .So a get accessor should be mapped to a couple of messages.
    Proposed solution :
    Define the incoming message as a message without any parameter as the following:
    <message name="MyAttrs._get_strAttr" />
    <message name="MyAttrs._get_strAttrResponse" >
    <part name="_return" type="xsd:string"/>
    </message>
    ¡­
    <portType name="MyAttrs" >
    <operation name="_get_strAttr" >
    <output message="tns:MyAttrs._get_strAttrResponse"/>
    <fault message=¡±tns:CORBA.SystemException¡±/>
    </operation>

  • Reported: C2WSDL 1.0 — Thu, 19 Feb 2004 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.1
  • Disposition Summary:

    Accept proposal from source

  • Updated: Sat, 7 Mar 2015 03:58 GMT

'CORBA to WSDL/SOAP Section 1.2.8.2

  • Legacy Issue Number: 6994
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Section 1.2.8.2
    In the example:
    <message name="CORBA.SystemExceptionMessage" >
    <part name="_return" type="CORBA.SystemException"/>
    </message>
    CORBA Specification says that CORBA Exception cannot be passed as paramters or return value. But the example seems to ¡°return¡± a SystemException.
    Proposed solution: Maybe the example should be defined as the following according to the exception mapping rules:
    <message name="CORBA.SystemExceptionMessage" >
    <part name="exception" type="CORBA.SystemException"/>
    </message>

  • Reported: C2WSDL 1.0 — Thu, 19 Feb 2004 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.1
  • Disposition Summary:

    Close with no change. While confusing, the use of "_return" for the name is not invalid

  • Updated: Sat, 7 Mar 2015 03:58 GMT

'CORBA to WSDL/SOAP: example for operation mapping

  • Legacy Issue Number: 6995
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Section 1.2.8.2
    Also, in the example for operation mapping.
    <portType name="SomeInterface" >
    <operation name="bar" >
    <input message="tns:SomeInterface.bar"/>
    <output message="tns:SomeInterface.barResponse"/>
    <fault message=¡±tns:CORBA.SystemException¡±/>
    </operation>
    </portType>
    Here defines the fault message, yet its type is not CORBA.SystemExceptionMessage defined ahead, but CORBA.SystemException, which is defined as a complextype.
    Proposed solution: Maybe the following is right:
    <fault message=¡±tns:CORBA.SystemExceptionMessage¡±/>

  • Reported: C2WSDL 1.0 — Thu, 19 Feb 2004 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.1
  • Disposition Summary:

    Accept proposal from source

  • Updated: Sat, 7 Mar 2015 03:58 GMT

CORBA fixed types

  • Legacy Issue Number: 6613
  • Status: closed  
  • Source: cpan ( Francois Perrad)
  • Summary:

    CORBA fixed types are mapped to the XML Schema "decimal" type (not "integer")

    And the element "restriction" of the map becomes : <xsd:restriction base="xsd:decimal">

    The xsd:integer type have a facet fractionDigits fixed to 0.

  • Reported: C2WSDL 1.0 — Thu, 13 Nov 2003 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.1
  • Disposition Summary:

    : Accept solution proposed by source

  • Updated: Sat, 7 Mar 2015 03:58 GMT