Name: krT82822 Date: 02/08/2000


(see also 4290690)

D:\priv>java -fullversion
java full version "1.3.0rc1-T"

The RMI-IIOP Tie skeletons produced by 'rmic -iiop' currently extend
org.omg.CORBA_2_3.portable.ObjectImpl.

These skeletons do not correspond to the format of a TIE based skeleton as
defined by the OMG in the IDL to Java Language Mapping Specification
( ftp://ftp.omg.org/pub/docs/formal/99-07-57.pdf ) in section 1.20.2.6
which states the correct (OMG approved) format for a delegation (TIE) based
server-side skeleton.

This is causing us problems for the following reasons:

My company (PeerLogic) ( http://www.peerlogic.com ) has a Java ORB which
is CORBA 2.3 compliant in the way described and implements POAs and supports
TIE based skeletons as described in 1.20.2.6 of the referenced document.

We would like to be able to support the use of RMI server classes which
use our CORBA implementation, but the current skeleton classes will *not* run
with our CORBA2.3 compliant implementation.

Note that using 'rmic -idl' to generate the IDL files, and then compiling
the IDL files using our IDL compiler does *not* provide a solution since this
critically does *not* generate the name-unmangling routines which are present
in the class generated from 'rmic -iiop -keep'

Note also that ths is *not* a request for any run-time enhancement to
the JavaSoft-supplied CORBA implementation, since once we have the required
skeleton classes we will use our own CORBA implementation.

(I would additionally be curious to know what JavaSoft's plans are for making
the JavaSoft supplied CORBA runtime properly CORBA 2.3 compliant. If anyone
in JavaSoft would be prepared to discuss this in any way, I would appreciate
being contacted)

We are currently sizing the work involved in writing an EJB container that
supports RMI-IIOP and which uses our CORBA implementation and this issue
is presenting a signigficant obstacle.
(Review ID: 100952)
======================================================================