Issue 2483: NotSerializableException for RMI-IIOP (java2idl-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: If a user passes a non-remote and non-serializable object to a remote method whose signature type is an abstract interface, the IBM/Sun implementation of RMI-IIOP currently returns a ClassCastException. It is not very obvious to the user what is causing this error. RMI-JRMP returns a NotSerializableException in this case, which is much easier for the user to interpret. Resolution: Closed, accepted Revised Text: In section 28.4.8, say that the CORBA BAD_PARAM system exception maps to java.rmi.MarshalException. If the BAD_PARAM minor code is 6 (as proposed to the core RTF in issue 2502), then the nested exception is java.io.NotSerializableException. For all other minor codes, the nested exception is the original BAD_PARAM. Actions taken: February 22, 1999: received issue June 4, 1999: closed issue Discussion: End of Annotations:===== Date: Mon, 22 Feb 1999 17:20:22 +0000 From: Simon Nash Organization: IBM To: issues CC: java2idl Subject: NotSerializableException for RMI-IIOP If a user passes a non-remote and non-serializable object to a remote method whose signature type is an abstract interface, the IBM/Sun implementation of RMI-IIOP currently returns a ClassCastException. It is not very obvious to the user what is causing this error. RMI-JRMP returns a NotSerializableException in this case, which is much easier for the user to interpret. It would be good to make RMI-IIOP throw the same exception in this case. However, this exception is not declared in the throws clause of either Util.writeAbstractObject or OutputStream.write_Abstract. Some signature change to at least the first of these would be necessary to support this. 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