1. OMG Mailing List
  2. IDL4 to Java Language Mapping (IDL4-JAVA) 1.0 Finalization Task Force

Open Issues

  • Issues not resolved
  • Name: idl4-java-ftf
  • Issues Count: 7

Issues Descriptions

Section 7.1.1.1 Name Transformation Rules

  • Key: IDL4JAV-4
  • Status: open   Implementation work Blocked
  • Source: Objective Interface Systems ( Chuck Abbott)
  • Summary:

    The section provides ambiguous guidance on name mapping from IDL to Java 8.

  • Reported: IDL4-Java 1.0a1 — Thu, 26 Sep 2019 14:02 GMT
  • Updated: Wed, 19 Feb 2020 22:34 GMT

Typo fixes

  • Key: IDL4JAV-7
  • Status: open  
  • Source: Airbus Group ( Oliver Kellogg)
  • Summary:

    In section 7.2.4.2.1.1 on page 13 top of page after end of fixed font Java code:

    Where:
    • <IntarfaceName> is the interface name indicated in Table 7.4.

    <IntarfaceName> should be <InterfaceName>

    In section 7.2.4.3.2 on page 16 paragraph before the union U1 example:

    [...] The first modifier method shall
    take no arguments, return void, and setsthe discriminant to the first available default value starting from a 0 index of the
    discriminant type.

    setsthe should be set the.

    In section 8.1.3 table 8.2 column "IDL Construct", repeated typo:
    Accesor should be Accessor.
    In particular, on page 32:

    Structure Member Name in
    Accesor/Modifier Methods

    Union Member Name in
    Accesor/Modifier Methods

    and on page 33:

    Interface Attribute Name in
    Accesor/Modifier Methods

    Exception Member Name in
    Accesor/Modifier Methods

    Bitfield Name in Bitset
    Accesor/Modifier Methods

  • Reported: IDL4-Java 1.0a1 — Mon, 30 Dec 2019 12:49 GMT
  • Updated: Tue, 7 Jan 2020 12:58 GMT

Constants mapping is incomplete/broken

  • Key: IDL4JAV-5
  • Status: open   Implementation work Blocked
  • Source: Objective Interface Systems ( Chuck Abbott)
  • Summary:

    The constant mapping is prone to namespace collision

  • Reported: IDL4-Java 1.0a1 — Thu, 26 Sep 2019 14:06 GMT
  • Updated: Tue, 10 Dec 2019 22:27 GMT

Address the CORBA specific mapping[s]

  • Key: IDL4JAV-2
  • Status: open  
  • Source: Twin Oaks ( Clark Tucker)
  • Summary:

    For example, these building blocks, etc:

    • CORBA specific interfaces
    • "Any" type
    • CORBA specific value-type
    • System Exception
    • Pseudo Objects [may remove]
    • org.omg package
  • Reported: IDL4-Java 1.0a1 — Tue, 24 Sep 2019 18:28 GMT
  • Updated: Tue, 10 Dec 2019 22:02 GMT

Interfaces - Full should define a FooOperations interface

  • Key: IDL4JAV-6
  • Status: open  
  • Source: Real-Time Innovations ( Fernando Garcia-Aranda)
  • Summary:

    Interfaces - Full should define a FooOperations interface like we have done in the IDL to C# Language Mapping.

    Also, public abstract void op1(S sIn); should be changed to void op1(S sIn);.

  • Reported: IDL4-Java 1.0a1 — Tue, 10 Dec 2019 21:57 GMT
  • Updated: Tue, 10 Dec 2019 21:59 GMT

Package prefix specified at the IDL to Java translator

  • Key: IDL4JAV-1
  • Status: open  
  • Source: Airbus Group ( Oliver Kellogg)
  • Summary:

    Predecessor: https://issues.omg.org/browse/I2JAV13-11

    Many of the IDL to Java translators support an option to specify a Java package prefix for the generated code (e.g. Oracle idlj option -pkgPrefix; JacORB option -i2jpackage; rtiddsgen option -package).
    This is not exactly equivalent to hard coding the prefix as modules in the IDL: When using the translator option, other language mappings do not see the prefix.

    The package prefix provided to the IDL translator may produce a conflict with names in the IDL file.
    Example:

    // file: test.idl
    module test {
    
       enum com_t { zero, one };
    
       struct org_t {
          short foo;
       };
    
       typedef string<16> net_t;
    
       struct structure {
          com_t com;   // "com" is in conflict when providing prefix option such as: com.acme
          org_t org;   // "org" is in conflict when providing prefix option such as: org.acme
          net_t net;   // "net" is in conflict when providing prefix option such as: net.acme
       };
    
    };
    

    Notice that the Java generated for this IDL does not compile but it does compile for other languages (C++, Ada, etc).

    Section 7.1.1.1 (Name Transformation Rules) contains:

    If the mapped name or identifier collides with a reserved name in 7.1.2, the collision is resolved by prepending an underscore ("_") to the mapped name.

    I suggest adding a further sentence:

    This also applies to name collisions caused by a Java package prefix specified at the IDL to Java translator.
    
  • Reported: IDL4-Java 1.0a1 — Tue, 13 Aug 2019 15:34 GMT
  • Updated: Tue, 10 Dec 2019 21:36 GMT

Provide additional flexibility in language mapping

  • Key: IDL4JAV-3
  • Status: open  
  • Source: Twin Oaks ( Clark Tucker)
  • Summary:

    Concerns/Thoughts:

    • namespace prefix flexibility
    • compatibility with CORBA IDL
    • possible additions to the java mapping annotation to adjust the language mapping
  • Reported: IDL4-Java 1.0a1 — Tue, 24 Sep 2019 19:16 GMT
  • Updated: Tue, 24 Sep 2019 19:16 GMT