Issue 2535:  Mapping remote interface types to RMI-style repository IDs (java2idl-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: RMI remote interface types are currently mapped to IDL interfaces without
 a #pragma ID, which means they have IDL-style repository IDs.  This causes
 problems when trying to locate a "best match" RMI stub for an IOR that
 contains this format of repository ID.  Because of the non-reversible
 manglings from Java interface names to IDL interface names (inner classes,
 leading underscores, and Unicode characters), there is no reliable 
 demangling from the IDL-style repid in an IOR to an RMI stub class name.
 
 This can be fixed by using the RMI style of repid instead of the IDL style
 of repid when mapping RMI remote interfaces to IDL, just as we currently
 do for value types.
 

Resolution: Closed, accepted
Revised Text: In the mapping from RMI remote interfaces to IDL interfaces, add a
#pragma ID specifying an RMI: format repository ID derived from the Java
interface name using the rules specified in chapter 10, with a hash code
of zero and no SUID.
Actions taken:
March 15, 1999: received issue
June 4, 1999: closed issue
Discussion: 

End of Annotations:=====
Date: Sat, 13 Mar 1999 12:35:42 +0000
From: Simon Nash <nash@hursley.ibm.com>
Organization: IBM
X-Accept-Language: en
To: issues@omg.org
CC: java2idl-rtf@omg.org, Bryan Atsatt <atsatt@us.ibm.com>,
        Steve Lewallen <srlewall@us.ibm.com>
Subject: Mapping remote interface types to RMI-style repository IDs

RMI remote interface types are currently mapped to IDL interfaces
without
a #pragma ID, which means they have IDL-style repository IDs.  This
causes
problems when trying to locate a "best match" RMI stub for an IOR that
contains this format of repository ID.  Because of the non-reversible
manglings from Java interface names to IDL interface names (inner
classes,
leading underscores, and Unicode characters), there is no reliable 
demangling from the IDL-style repid in an IOR to an RMI stub class
name.

This can be fixed by using the RMI style of repid instead of the IDL
style
of repid when mapping RMI remote interfaces to IDL, just as we
currently
do for value types.


Proposed Resolution:

In the mapping from RMI remote interfaces to IDL interfaces, add a
#pragma ID specifying an RMI: format repository ID derived from the
Java
interface name using the rules specified in chapter 10, with a hash
code
of zero and no SUID.


   Simon
-- 
Simon C Nash, Technology Architect, IBM Java Technology Centre
Tel. +44-1962-815156   Fax +44-1962-818999    Hursley, England
Internet: nash@hursley.ibm.com   Lotus Notes: Simon Nash@ibmgb