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: 5

Issues Descriptions

Naming Conventions and Transformation Rules

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

    Section 7.1.1.1 provides ambiguous guidance on name mapping from IDL to Java 8.

    We should adopt the solution agreed upon for the IDL to C# Language Mapping.

    On a side note, many Java snippets use semicolons at the end of a class declaration, which is unnecessary in Java.

  • Reported: IDL4-Java 1.0a1 — Thu, 26 Sep 2019 14:02 GMT
  • Updated: Mon, 13 Jul 2020 14:32 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: Mon, 13 Jul 2020 14:32 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: Mon, 13 Jul 2020 14:32 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: Mon, 13 Jul 2020 14:32 GMT

Provide additional flexibility in language mapping

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

    This issue is a placeholder for any feature request in terms of namespace prefix flexibility, compatibility with CORBA IDL, or possible additions to the java mapping annotation to adjust the language mapping.

    This issue should be closed with no change if no such features or concerned are filed.

  • Reported: IDL4-Java 1.0a1 — Tue, 24 Sep 2019 19:16 GMT
  • Updated: Mon, 13 Jul 2020 14:32 GMT