Issue 1662: read_AbstractObject and write_AbstractObject (java2idl-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: In section 7.1.2, there is a method called read_AbstractObject(clz). I propose that we change its name to read_Abstract to bring it into line with the read_Abstract() method introduced in section 8.7.1 of the OBV spec. This is consistent with having methods called read_Object() and read_Object(clz). There"s also a typo in section 7.2.6. It says that Util.write_AbstractObject calls OutputStream.write_AbstractObject. This should say OutputStream.write_Abstract. Resolution: Revised Text: Actions taken: July 10, 1998: received issue February 23, 1999: closed issue Discussion: End of Annotations:===== Return-Path: Date: Fri, 10 Jul 1998 08:46:23 +0100 From: Simon Nash Reply-To: nash@hursley.ibm.com Organization: IBM To: java2idl-rtf@omg.org Cc: java-rtf@omg.org, issues@omg.org Subject: read_AbstractObject and write_AbstractObject This item arises from the Java-to-IDL Mapping RFP, but is also of concern to the IDL-to-Java RTF because it affects the IDL-to-Java mapping. In section 7.1.2, there is a method called read_AbstractObject(clz). I propose that we change its name to read_Abstract to bring it into line with the read_Abstract() method introduced in section 8.7.1 of the OBV spec. This is consistent with having methods called read_Object() and read_Object(clz). There's also a typo in section 7.2.6. It says that Util.write_AbstractObject calls OutputStream.write_AbstractObject. This should say OutputStream.write_Abstract. 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