Issue 2111: mapping from java.rmi Remote to CORBA::Object (java2idl-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: Are we trying to support sending JRMP stubs over IIOP? If so, then it would seem that the IDL mapping of java.rmi.Remote to CORBA::Object works against that; it would need to be changed to Any. Resolution: See revised text below. Revised Text: In section 1.5.1.4, at the end of the paragraphs describing writeRemoteObject and writeAbstractObject, add the sentence: "This method cannot be used to write a JRMP object reference to an output stream." Actions taken: October 20, 1998: received issue May 24, 2001: closed issue Discussion: End of Annotations:===== Return-Path: Date: Tue, 20 Oct 1998 16:44:53 +0100 From: Simon Nash Organization: IBM To: issues@omg.org Subject: [Fwd: mapping java.rmi.Remote to CORBA::Object] Please add this to the issues database. You added the other Java to IDL issues I sent on Friday, but not this one. Thanks. Simon -- Simon C Nash, IBM Java Technology Centre, Hursley, UK MailPoint 146, x245156 Tel. 01962 815156 or +44-1962-815156 Internet: nash@hursley.ibm.com Notes mail: Simon Nash@ibmgbMessage-ID: <362778AF.6EA1EF2A@hursley.ibm.com> Date: Fri, 16 Oct 1998 17:47:43 +0100 From: Simon Nash Organization: IBM X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: issues@omg.org CC: java2idl-rtf@omg.org Subject: mapping java.rmi.Remote to CORBA::Object Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The following Java to IDL issue was raised by Bob Scheifler. It needs to be added to the issues database. Are we trying to support sending JRMP stubs over IIOP? If so, then it would seem that the IDL mapping of java.rmi.Remote to CORBA::Object works against that; it would need to be changed to Any. Simon -- Simon C Nash, IBM Java Technology Centre, Hursley, UK MailPoint 146, x245156 Tel. 01962 815156 or +44-1962-815156 Internet: nash@hursley.ibm.com Notes mail: Simon Nash@ibmgb Date: Sun, 12 Nov 2000 14:22:45 +0000 From: Simon Nash Organization: IBM X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: java2idl-rtf@omg.org Subject: Issue 2111 proposed resolution Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: pK7e9=RNe9BD~!!02U!! I will place the following proposed resolution for issue 2111 in vote 2 of the Java to IDL RTF unless I hear otherwise by close of business Wednesday. Discussion: Changing the mapping of java.rmi.Remote from Object to any would be a major incompatibility and realistically is not an option. Therefore this issue as currently worded should be closed no change. If there is a requirement to send JRMP stubs across RMI-IIOP (and so far we have not seen user demand for this), then another approach that does not change the Java to IDL mapping should be used. For example, JRMP stubs could be serialized as IORs with a JRMP profile. Proposed Resolution: Close, no change. 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 Date: Mon, 13 Nov 2000 09:50:22 -0500 (EST) From: Bob Scheifler - SMI Software Development Reply-To: Bob Scheifler - SMI Software Development Subject: Re: Issue 2111 proposed resolution To: nash@hursley.ibm.com Cc: java2idl-rtf@omg.org MIME-Version: 1.0 Content-MD5: KNFExB4ai5q0pGt7DXcIGQ== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc Content-Type: TEXT/plain; charset=us-ascii X-UIDL: ;hL!!GO]!!H*B!!J%Ce9 > Changing the mapping of java.rmi.Remote from Object to any would be a major > incompatibility and realistically is not an option. Therefore this issue as > currently worded should be closed no change. At least document this lame outcome in section 1.4.12. - Bob Date: Mon, 13 Nov 2000 22:38:12 +0000 From: Simon Nash Organization: IBM X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: Bob Scheifler - SMI Software Development CC: java2idl-rtf@omg.org Subject: Re: Issue 2111 proposed resolution References: <200011131447.JAA17007@eastmail1.East.Sun.COM> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: DB\d9oKE!!"+e!!cROd9 Bob, I'm sorry that you think this is a lame outcome. We could leave this issue permanently open, but I don't see any value in this. I am not ruling out passing JRMP stubs across IIOP, but in order for this to fly we would (IMO) need to find a different approach that does not change the IDL mapping of the java.rmi.Remote type. If you would like to submit a fully worked out proposal that is upwards compatible with the current spec, we will consider it and vote on it. Regarding the documentation of this limitation, this isn't the same situation as the other cases documented in 1.4.12. This section lists JRMP semantics that cannot be supported by IIOP. In this case, the JRMP semantics can be supported (i.e., references to remote objects can be passed). It is the JRMP implementation of stubs that cannot be passed. A more appropriate place to add a comment about this current limitation is section 1.5.1.4. At the end of the paragraphs describing writeRemoteObject and writeAbstractObject, we could add the sentence: "This method cannot be used to write a JRMP object reference to an output stream." Simon Bob Scheifler - SMI Software Development wrote: > > > Changing the mapping of java.rmi.Remote from Object to any would be a major > > incompatibility and realistically is not an option. Therefore this issue as > > currently worded should be closed no change. > > At least document this lame outcome in section 1.4.12. > > - Bob -- 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