CORBA to WSDL/SOAP Interworking Avatar
  1. OMG Specification

CORBA to WSDL/SOAP Interworking — Closed Issues

  • Acronym: C2WSDL
  • Issues Count: 8
  • 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-WSDL/SOAP: Section 1.2.7.4

  • Legacy Issue Number: 5793
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    The mapping does not state what value should be used for the default
    case.

    Proposed Resolution:
    Add text stating that any valid value for the discriminant, other than
    those used
    in the union definition, can be inserted for the default case.

  • Reported: C2WSDL 1.0b1 — Wed, 18 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    Accept proposal from source

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

CORBA-WSDL/SOAP: section 1.2.8.2 , 1.2.8.4 and 1.2.8.5

  • Legacy Issue Number: 5792
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    section 1.2.8.2 , 1.2.8.4 and 1.2.8.5 - In all the Example WSDL, the
    target namespace in definitions and the namespace in import using URL
    "http://tempuri.org/anExample/.." do not seem correct.

    Proposed Resolution: fix the example after resolving the Type prefix FTF

    issue on namespace and module name uniqueness.

  • Reported: C2WSDL 1.0b1 — Tue, 17 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    Fix the examples to use the correct target namespace url

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

CORBA-WSDL/SOAP: Section 1.2.7.10

  • Legacy Issue Number: 5790
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Section 1.2.7.10 ­
    Only public state members are mapped. Since use of the Dynamic Any api
    allows access to both the private
    and public members, this restriction was challenged by the AB reviewer
    as unwarranted.
    Also the sentence "For example, DII/DSI bridges will be unable to
    process value types." is not justified.

    The dynamic ANY api can be used to access value type state members in a
    DII/DSI based gateway.
    If private state cannot be represented, an input value type parameter
    which has private state will not be mapped to the IDL server.

    Proposed Solution:
    Delete offending sentence about dynamic gateways.
    Unless the private member restriction can be justified, change the spec
    to map both private and public value type state members.

  • Reported: C2WSDL 1.0b1 — Wed, 18 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    Remove the restriction of not mapping Private state members

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

CORBA-WSDL/SOAP: Section 1.2.7.10.3

  • Legacy Issue Number: 5791
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Section 1.2.7.10.3 - need to represent value type in IDL sequence as an
    IdRef/value choice.

    Proposed Resolution:
    fix spec to use the idRef/Value choice for sequence<valueType>.

  • Reported: C2WSDL 1.0b1 — Tue, 17 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    see above

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

CORBA-WSDL/SOAP: section 1.2.4

  • Legacy Issue Number: 5788
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    section 1.2.4 - The sentence "The most significatn is that XML flattens
    the constructed namespace to a single targeted namespace when an XML
    schema is imported." does not seem quite correct. Avoiding a large
    number of files for the wsdl processor to deal with is a major reason
    cited by the submitters.

    Proposed Solution: Replace the offending sentence, with: "Having a
    separate namespace for each imported module results in a large number of

    files for the WSDL processor to deal with when constructing a gateway."

  • Reported: C2WSDL 1.0b1 — Tue, 17 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    Agree to editorial fix

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

Section 1.2.3 repository id inconsistency

  • Legacy Issue Number: 5787
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Section 1.2.3 - there is an inconsistency, in that the documentation
    schema for the repository ID dos not include the version of the mapping,

    as included in the URL source documentation schema.
    Knowing what version of the IDL to WSDL mapping produced the WSDL is
    important for gateway design.

    Proposed Resolution: add mapping version to the respositoryID
    documentation schema.

  • Reported: C2WSDL 1.0b1 — Tue, 17 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    Add mapping version to the repositoryID documentation schema

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

CORBA-WSDL/SOAP: Section 1.2.2.1

  • Legacy Issue Number: 5785
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Section 1.2.2.1 -
    tns is a single namespace for all mapped IDL from the entire corba
    world.
    The module names for IDL across this vast namespace, need to be
    sufficiently qualified with pre-fixes (such as Type ID, or Pragma
    Prefix) to avoid module name collisions.

    Proposed Resolution: FTF needs to determine appropriate prefixes or
    namespaces to assure module name uniqueness in the generated WSDL

  • Reported: C2WSDL 1.0b1 — Tue, 17 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    see above

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

CORBA-WSDL/SOAP: Section 1.2.3

  • Legacy Issue Number: 5786
  • Status: closed  
  • Source: Fujitsu ( Tom Rutt)
  • Summary:

    Section 1.2.3 - need to have appropriate text to describe the nature of
    the source "hint". Examples might be included, using filenames.

    Proposed Resolution: FTF should determine appropriate text.

  • Reported: C2WSDL 1.0b1 — Tue, 17 Dec 2002 05:00 GMT
  • Disposition: Resolved — C2WSDL 1.0
  • Disposition Summary:

    The nature of the hint can remain an implementation specific matter

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