Issue 4158: publication of messaging / unchecked_narrow (java-rtf) Source: UBS (Mr. Hans Kneubuehl, hans.kneubuehl(at)ubs.com) Nature: Uncategorized Issue Severity: Summary: Incorporate Messaging changes relevant to the Java mapping, as shown in orbos/98-05-05 pages 115 and 116 together with any changes made to them by the Messaging RTF, into the IDL-Java mapping chapter. Resolution: see below Revised Text: Replace 1.5.2 second paragraph with: The helper class for a mapped IDL interface or abstract interface also has narrow and unchecked_narrow operation(s) define in the template below. In section 1.5.2, in the generated java helper code: For each narrow method, add an identical unchecked_narrow method with the same parameters are the narrow method. In section 1.12.1, add the following paragraph after the fourth paragraph: The helper class holds a static unchecked_narrow method that allows an org.omg.CORBA.Object to be narrowed to the object reference of a more specific type. No type-checking is performed to verify that the object actually supports the requested type. The IDL exception CORBA::BAD_OPERATION can be expected if unsupported operations are invoked on the new returned reference, but no failure is expected at the time of the unchecked_narrow. Actions taken: January 19, 2001: received issue May 13, 2002: closed issue Discussion: End of Annotations:===== Date: Fri, 19 Jan 2001 11:16:20 -0500 From: Jishnu Mukerji Organization: Hewlett-Packard EIAL, Florham Park NJ USA X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: hans.kneubuehl@ubs.com, Juergen Boldt Cc: cxx_revision@omg.org, java-rtf@omg.org Subject: Re: publication of messaging / unchecked_narrow References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: PC#!!f_Ae9O` > CORBA Messaging has been published as part of CORBA 2.4. However, the adopted > CORBA Messaging specs also make changes to the C++ and Java language mappings. > In particular, orbos/98-05-05 on pages 115 and 116, specifies a new operation > unchecked_narrow(). > > Is this conformant with OMG policies and procedures? > Shouldn't specifications that are concerned by a newly available specifcation, > be published in synchronization? > How will the published specifications be aligned? Hans, Thanks for bringing this to our attention. Juergen, Please create two separate issues, one for C++ RTF and the other for Java RTF, the first one saying: Incorporate Messaging changes relevant to the C++ mapping, as shown in orbos/98-05-05 pages 115 and 116 together with any changes made to them by the Messaging RTF, into the IDL-C++ mapping chapter. and the second one saying: Incorporate Messaging changes relevant to the Java mapping, as shown in orbos/98-05-05 pages 115 and 116 together with any changes made to them by the Messaging RTF, into the IDL-Java mapping chapter. Thanks, Jishnu. From: hans.kneubuehl@ubs.com X-OpenMail-Hops: 2 Date: Fri, 19 Jan 2001 15:54:37 +0100 Message-Id: Subject: publication of messaging / unchecked_narrow MIME-Version: 1.0 TO: cxx_revision@omg.org, java-rtf@omg.org Content-Disposition: inline; filename="BDY.TXT" ;Creation-Date="Fri, 19 Jan 2001 15:54:36 +0100" Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-UIDL: :p9e9Q+T!!HJ_d92d'e9 CORBA Messaging has been published as part of CORBA 2.4. However, the adopted CORBA Messaging specs also make changes to the C++ and Java language mappings. In particular, orbos/98-05-05 on pages 115 and 116, specifies a new operation unchecked_narrow(). Is this conformant with OMG policies and procedures? Shouldn't specifications that are concerned by a newly available specifcation, be published in synchronization? How will the published specifications be aligned? Regards Hans -- Hans Kneubuehl, UBS AG, P.O. Box, 8098 Zurich, Switzerland phone: +41 1 238 28 96, fax: +41 1 238 30 11 Date: Tue, 11 Dec 2001 23:05:06 -0800 (PST) From: Ken Cavanaugh Reply-To: Ken Cavanaugh Subject: Proposal for issue 4158 To: java-rtf@omg.org MIME-Version: 1.0 Content-MD5: mvHwQFFVaTjH9ZRI1mpRYA== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc Content-Type: TEXT/plain; charset=us-ascii X-UIDL: >M^!!Bl^d9Jk,e9""H!! Since messaging has been incorporated into the CORBA specification, we need to provide support for the unchecked_narrow operation defined in the specification (orbos/98-05-05 page 115-116). This requires the following changes: Replace 1.5.2 second paragraph with: The helper class for a mapped IDL interface or abstract interface also has narrow and unchecked_narrow operation(s) define in the template below. In section 1.5.2, in the generated java helper code: For each narrow method, add an identical unchecked_narrow method with the same parameters are the narrow method. In section 1.12.1, add the following paragraph after the fourth paragraph: The helper class holds a static unchecked_narrow method that allows an org.omg.CORBA.Object to be narrowed to the object reference of a more specific type. No type-checking is performed to verify that the object actually supports the requested type. The IDL exception CORBA::BAD_OPERATION can be expected if unsupported operations are invoked on the new returned reference, but no failure is expected at the time of the unchecked_narrow. Ken.