I2JAV 1.2 NO IDEA Avatar
  1. OMG Issue

I2JAV12 — attribute exceptions

  • Key: I2JAV12-23
  • Legacy Issue Number: 4793
  • Status: closed  
  • Source: Oracle ( Ken Cavanaugh)
  • Summary:

    The CCM (ptc/01-11-03) has added exceptions to attributes.
    The IDL to Java mapping needs to be updated to reflect this addition.
    Also, the mapping currently says essentially nothing about the mapping of
    exceptions
    on operations or attributes in any context.

    Proposed revised text:

    In section 1.13.2, replace the paragraph

    The mapped Java class contains abstract method definitions that correspond
    to the operations and attributes defined on the value type in IDL.

    with

    The mapped Java class contains abstract method definitions that correspond
    to the operations and attributes defined on the value type in IDL.
    Attributes
    are mapped in the same way as in interfaces, to modifer and accessor
    methods.
    Exceptions are mapped as follows:

    1. If an operation raises exceptions, then the corresponding Java method
    must throw
    Java exceptions corresponding to the listed IDL exceptions.

    2. If a readonly attribute raises exceptions, then the Java read accessor
    method must throw
    Java exceptions corresponding to the listed IDL exceptions.

    3. If an attribute has a getRaises clause, the the Java accessor method must
    throw Java exceptions corresponding to the listed IDL exceptions.

    4. If an attribute has a setRaises clause, the the Java modifier method must
    throw Java exceptions corresponding to the listed IDL exceptions.

    In section 1.12.1, replace the third paragraph with the following two
    paragraphs:

    The Java operations interface contains the mapped operation signatures.
    If an operation raises exceptions, then the corresponding Java method must
    throw
    Java exceptions corresponding to the listed IDL exceptions.

    The Java signature interface extends the operations interface, the (mapped)
    base org.omg.CORBA.Object, as well as org.omg.portable.IDLEntity.
    Methods can be invoked on the signature interface. Interface inheritance
    expressed in IDL is reflected in both the Java signature interface and
    operations interface hierarchies.

    In section 1.12.1, insert after the sixth paragraph:

    Attribute exceptions are mapped as follows:

    1. If a readonly attribute raises exceptions, then the Java read accessor
    method must
    throw Java exceptions corresponding to the listed IDL exceptions.

    2. If an attribute has a getRaises clause, the the Java accessor method must
    throw Java exceptions corresponding to the IDL exceptions listed in the
    getRaises clause.

    3. If an attribute has a setRaises clause, the the Java modifier method must
    throw Java exceptions corresponding to the IDL exceptions listed in the
    setRaises clause.

  • Reported: I2JAV 1.1 — Tue, 18 Dec 2001 05:00 GMT
  • Disposition: Resolved — I2JAV 1.2
  • Disposition Summary:

    Incoporate the revised text and close the issue

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