Issue 3641: Java to IDL mapping contradictive to CORBA/IIOP 2.3.1 (java2idl-rtf) Source: (, ) Nature: Clarification Severity: Significant Summary: The Java to IDL Language Mapping (formal/99-07-59) seems to contradict the CORBA/IIOP 2.3.1 Specification (formal/99-10-07) over exceptions being raised by valuetype initialisers. Section 1.3.5.4 of 99-07-59, point 3 states that exceptions thrown by a constructor of an object-by-value class are mapped to the corresponding OMG IDL exception. On the other hand, section 2.8.1.5 of 99-10-07 does not allow initialisers to include a raises clause (contrast this with the syntax for an operation declaration in section 3.12). This is a significant inter-operability problem. In my case the IDL generated by the IBM/SUN RMI-IIOP Java-to-IDL compiler (which includes 'raises' clauses in valuetype initialisers) is rejected as syntactically invalid by the MICO IDL-to-C++ compiler. submit: Submit Issue Report Resolution: Close, no change. Core RTF issue 4785 has added exceptions to IDL valuetype initializers, which reso Revised Text: Actions taken: May 24, 2000: received issue May 13, 2002: closed issue Discussion: This issue could be resolved by adding exceptions to initializers in the CORBA core spec. However, the core RTF recently voted to close issue 3781 with no change because they considered adding exceptions to initializers to be out of scope for an RTF since it is not a bug fix. Also, it is very dificult to do this without causing incompatibilities in the IR interfaces in the CORBA module that deal with initializers. However, the Components RFP is adding an ExtendedIR module to accommodate the IR changes needed for CCM, and it is possible that the Java to IDL RTF could work with the Components FTF to add exceptions on initializers in the ExtendedIR module as part of CORBA 3.0 (though this change is not motivated by a components issue). One problem with this approach is that adding exceptions on initializers in CORBA 3.0 does not resolve the current broken state of the Java to IDL mapping in this area for CORBA 2.x. Before taking this issue any further with other RTFs or FTFs I would like to know if the Java to IDL RTF wants to pursue getting exceptions on initializers added to the core spec. Please indicate your preferred course of action by voting for either option A or option B below. A. Replace numbered paragraphs 3 and 4 in section 1.3.5.4 of the Java to IDL mapping spec by the following text: 3. Java exceptions are not mapped to IDL. B. Leave this issue open for now and work with other RTFs or FTFs to attempt to get the core spec changed to add exceptions to IDL initializers. End of Annotations:===== Date: Wed, 24 May 2000 08:55:23 -0400 (EDT) Message-Id: <200005241255.IAA20982@emerald.omg.org> From: brian.higgins@man.brite.co.uk To: juergen@omg.org, web-incoming@omg.org Subject: Issue Report Content-Type: text X-UIDL: @%De9UFK!!ejf!!i4Je9 Name: Brian Higgins Company: Intervoice-Brite Inc. mailFrom: brian.higgins@man.brite.co.uk Notification: Yes Specification: Java to IDL Language Mapping Section: 1.3.5.4 Formal #: 99-07-59 Version: New Edition Revision_Date: June 1999 Page: 1-15 Nature: Clarification Severity: Significant full_desc: The Java to IDL Language Mapping (formal/99-07-59) seems to contradict the CORBA/IIOP 2.3.1 Specification (formal/99-10-07) over exceptions being raised by valuetype initialisers. Section 1.3.5.4 of 99-07-59, point 3 states that exceptions thrown by a constructor of an object-by-value class are mapped to the corresponding OMG IDL exception. On the other hand, section 2.8.1.5 of 99-10-07 does not allow initialisers to include a raises clause (contrast this with the syntax for an operation declaration in section 3.12). This is a significant inter-operability problem. In my case the IDL generated by the IBM/SUN RMI-IIOP Java-to-IDL compiler (which includes 'raises' clauses in valuetype initialisers) is rejected as syntactically invalid by the MICO IDL-to-C++ compiler. submit: Submit Issue Report Date: Tue, 18 Dec 2001 20:22:47 +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 CC: orb_revision@omg.org Subject: Proposed resolution for issue 3641 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: 8kIe9IA5e99;f!!E@$!! Core issue 4785 proposes adding exceptions to IDL valuetype initializers. If adopted, this will resolve Java to IDL issue 3641, which states that Java constructor exceptions are mapped to IDL valuetype initializer exceptions. The proposed resolution for issue 3641 is to close it with no change, noting that the resolution to issue 4785 takes care of the problem. Many thanks for Jishnu for his help with resolving this issue. Simon -- Simon C Nash, Chief Technical Officer, IBM Java Technology Tel. +44-1962-815156 Fax +44-1962-818999 Hursley, England Internet: nash@hursley.ibm.com Lotus Notes: Simon Nash@ibmgb