Issue 1640: Should Portability APIs throw SystemException? (java2idl-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: 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. Three of the new portability APIs intorduced by the Java to IDL mapping are declared as throwing org.omg.CORBA.SystemException. These are the _invoke methods of ObjectImpl and Delegate and the _invoke method of InvokeHandler. I don"t think this exception hould be declared explicitly, since it is a subclass of java.lang.RuntimeException and so is always implictly throwable whether it is declared or not. Also, other portability APIs can throw this exception even though they do not declare it explicitly. This inconsistency makes it very difficult for the reader of the spec to determine which of the portability APIs can throw CORBA system exceptions, and is likely to cause confusion. I propose that org.omg.CORBA.SystemException be removed from the throws clause of the above-mentioned APIs. Resolution: Revised Text: Actions taken: July 8, 1998: received issue February 23, 1999: closed issue Discussion: End of Annotations:===== Return-Path: Date: Tue, 07 Jul 1998 12:10:57 +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: Should portability APIs throw SystemException 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. Three of the new portability APIs intorduced by the Java to IDL mapping are declared as throwing org.omg.CORBA.SystemException. These are the _invoke methods of ObjectImpl and Delegate and the _invoke method of InvokeHandler. I don't think this exception hould be declared explicitly, since it is a subclass of java.lang.RuntimeException and so is always implictly throwable whether it is declared or not. Also, other portability APIs can throw this exception even though they do not declare it explicitly. This inconsistency makes it very difficult for the reader of the spec to determine which of the portability APIs can throw CORBA system exceptions, and is likely to cause confusion. I propose that org.omg.CORBA.SystemException be removed from the throws clause of the above-mentioned APIs. 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