IDL to Java Language Mapping Avatar
  1. OMG Specification

IDL to Java Language Mapping — Open Issues

  • Acronym: I2JAV
  • Issues Count: 5
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Java source code for org.omg.PortableServer.POAOperations

  • Key: I2JAV13-7
  • Legacy Issue Number: 5646
  • Status: open  
  • Source: SAS Institute Inc. ( Biff Beers)
  • Summary:

    The Java source code for org.omg.PortableServer.POAOperations in ptc/02-06-14 defines the method create_reference_with_id as throwing org.omg.PortableServer.POAPackage.WrongPolicy. However, the CORBA/IIOP 2.4 specification (formal/00-10-01) specifies this operation as NOT raising any exceptions (see section Which is correct?

  • Reported: I2JAV 1.1 — Thu, 19 Sep 2002 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

section 1.21.3 IDLEntity

  • Key: I2JAV13-8
  • Legacy Issue Number: 9795
  • Status: open  
  • Source: at&t ( Dave Brink)
  • Summary: section 1.21.3 IDLEntity inclides the Serializable interface, but if an IDLEntity has a union, it will result in Holder classes (i.e. FloatHolder) which do not implement the Serializable interface. This results in NotSerializable exceptions being created when trying to use such objects with java serialization. The quick fix would be to specify that "public interface Streamable" should extend, since the holder classes extend from that as well.

  • Reported: I2JAV 1.1 — Fri, 26 May 2006 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

definition of FixedHolder should have been removed

  • Key: I2JAV13-4
  • Legacy Issue Number: 5893
  • Status: open  
  • Source: Objective Interface Systems ( Mr. Victor Giddings)
  • Summary:

    The resolution of issue #3668 should have removed the definition of FixedHolder. There is no need for a Holder for an anonymous Fixed type since none can be defined. Type specific Holders are necessary in order to define the correct read and write operations that use the write_fixed and read_fixed defined by the resolution of 3668.

    Proposed resolution:
    Remove the definition of FixedHolder from section (page 1-11).

  • Reported: I2JAV 1.1 — Tue, 1 Apr 2003 05:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

J2EE ORB Socket Factory API

  • Key: I2JAV13-9
  • Legacy Issue Number: 5108
  • Status: open  
  • Source: International Business Machines ( Ann Collins)
  • Summary:

    In order to meet the interoperability compliance requirements,
    ORBs must include an IIOP implementation using TCP/IP plain text
    sockets. J2EE implementations are required to support CSIv2 and
    thus need additional control over the sockets an ORB creates.
    It may be necessary

    • to get the ORB to listen on additional sockets, of differing
    • to get the ORB to connect to alternative sockets, of different
      types, for a given IOR
    • for information about these sockets to be included in object
      references exported by the ORB
    • for socket data to be available to request interceptors, e.g
      SSL certificates

    Portable IORInterceptors can be used to add this information as
    tagged components in the profiles within an IOR.

    A mechanism is required to modify the ORB's behaviour to allow
    it to handle different socket types, listen on additional sockets,
    connect to alternative sockets and make additional data available
    to interceptors.

    Since this is a J2EE requirement which needs speedy resolution,
    it seems appropriate to resolve it by the addition of Java
    specific APIs in the IDL to Java specification. For example,

    • a pluggable ORB socket factory could be introduced which would
      be used whenever the ORB needed to create a serverSocket or an
      outbound socket for a given IOR or end point
    • a means of registering such a socket factory would be required.
      Options for this include:-
      . adding an ORB method: this may cause problems in initialisation
      . adding a Java specific extension to the PI ORBInitInfo interface
      so that the registration would need to be called from the
      pre_init/post_init methods in an ORBInitializer: this ties the
      Socket Factory with PIs, but both are likely to be required
      for J2EE.
    • a means of specifying ports on which an ORB/POA should listen
      would be useful but this may be infeasible as part of this issue
      due to the variety of ORB/POA implementations.
    • the PI Client and ServerRequestInfo and IORInfo interfaces may
      need to be extended to support access to Connection related data
  • Reported: I2JAV 1.1 — Tue, 9 Apr 2002 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

wrong enumeration value for SetOverrideType

  • Key: I2JAV13-5
  • Legacy Issue Number: 7846
  • Status: open  
  • Source: Objective Interface Systems ( Mr. Victor Giddings)
  • Summary:

    In ptc/02-01-01, the latest compendium of predefined code for the IDL to Java mapping, the enumerations values captured in org.omg.CORBA.SetOverrideType are SET_OVERRIDE and ADD. The correct values are SET_OVERRIDE and ADD_OVERRIDE.

  • Reported: I2JAV 1.1 — Thu, 7 Oct 2004 04:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT