Issue 3707: Need clarification on custructor(s) for stream-based (java-rtf) Source: Borland Software Corporation (Mr. Vijaykumar Natarajan, nobody) Nature: Uncategorized Issue Severity: Summary: In OMG IDL to Java Language Mapping spec, $1.21.5.1 "Stub/Skeleton Architecture" there are examples of stream- and DSI- based stubs/skeletons. These examples do not provide any constructors (this mean thay have only default ones). But, it seems that signatures of constructors should be clarified, because orb vendors have a freedom in defining these signatures. For example, the VisiBroker's 4.0 idl2java compiler generates stubs that have only default constructors, but in jdk 1.2 there stubs that have only constructors that take org.omg.CORBA.portable.Delegate as a single parameter. This leads to impossibility for generated stubs to extend the jdk 1.2 provided ones. Since the example is not normative, vendors are free to add whatever constructors they would like. This makes it impossible to generate code for interfaces that are inherited from interfaces for which code is generated by another vendor, which is true especially in the case of Java 2 and its inclusion of some stubs. I would like to propose the following: To Seciton 1.21.5.1 under subheading Stub Design, add a bullet: Stubs are not required to define any constructors. However, if they do define special constructors, a constructor with no arguments must also be defined. This ensures that all stubs are guaranteed to have the no argument constructor irrespective of whether they have other constructors or not. Resolution: see below Revised Text: To Section 1.21.5.1 under subheading Stub Design, add a bullet: Stubs are not required to define any constructors. However, if they do define special constructors, a constructor with no arguments must also be defined. Actions taken: June 14, 2000: received issue February 27, 2001: closed issue Discussion: End of Annotations:===== Date: Wed, 14 Jun 2000 11:25:34 -0700 From: "Vijaykumar Natarajan" X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: issues@omg.org, java-rtf@omg.org, mleland@fpk.hp.com Subject: [Fwd: Need clarification on custructor(s) for stream-based stubs/skeletons] Content-Type: multipart/mixed; boundary="------------0D6FCB95AA4BE4B94CDAF6EC" X-UIDL: F*S!!cD\!!7c$e9fA%e9 Hi all, I'd like to raise this as a formal issue. In OMG IDL to Java Language Mapping spec, $1.21.5.1 "Stub/Skeleton Architecture" there are examples of stream- and DSI- based stubs/skeletons. These examples do not provide any constructors (this mean thay have only default ones). But, it seems that signatures of constructors should be clarified, because orb vendors have a freedom in defining these signatures. For example, the VisiBroker's 4.0 idl2java compiler generates stubs that have only default constructors, but in jdk 1.2 there stubs that have only constructors that take org.omg.CORBA.portable.Delegate as a single parameter. This leads to impossibility for generated stubs to extend the jdk 1.2 provided ones. Since the example is not normative, vendors are free to add whatever constructors they would like. This makes it impossible to generate code for interfaces that are inherited from interfaces for which code is generated by another vendor, which is true especially in the case of Java 2 and its inclusion of some stubs. I would like to propose the following: To Seciton 1.21.5.1 under subheading Stub Design, add a bullet: Stubs are not required to define any constructors. However, if they do define special constructors, a constructor with no arguments must also be defined. This ensures that all stubs are guaranteed to have the no argument constructor irrespective of whether they have other constructors or not. Thanks, Vijay Gregory Kesler wrote: > In OMG IDL to Java Language Mapping spec, $1.21.51 "Stub/Skeleton Architecture" > there are examples of stream- and DSI- based stubs/skeletons. These examples do not > provide any constructors (this mean thay have only default ones). But, it seems that > signatures of constructors should be clarified, because orb vendors have a freedom > in defining these signatures. For example, the VisiBroker's 4.0 idl2java compiler > generates stubs that have only default constructors, but in jdk 1.2 there stubs that > have only constructors that take org.omg.CORBA.portable.Delegate as a single > parameter. This leads to impossibility for generated stubs to extend the jdk 1.2 > provided ones. Thanks. Gregory Return-Path: Received: from druid.inprise.com ([143.186.11.70]) by godzooky.inprise.com (Netscape Messaging Server 3.6) with ESMTP id AAA383F for ; Fri, 11 Feb 2000 16:51:33 -0800 Received: from messaging.inprise.com ([10.186.2.160]) by druid.inprise.com (8.8.8+Sun/8.8.7) with ESMTP id QAA04743 for ; Fri, 11 Feb 2000 16:49:25 -0800 (PST) Received: from druid.inprise.com ([143.186.11.70]) by messaging.inprise.com (Netscape Messaging Server 3.61) with ESMTP id AAA51A7 for ; Fri, 11 Feb 2000 16:53:42 -0800 Received: from emerald.omg.org (emerald.omg.org [192.67.184.65]) by druid.inprise.com (8.8.8+Sun/8.8.7) with ESMTP id QAA04735; Fri, 11 Feb 2000 16:49:21 -0800 (PST) Received: from druid.inprise.com (druid.inprise.com [143.186.11.70]) by emerald.omg.org (8.9.2/8.9.2) with ESMTP id TAA26401 for ; Fri, 11 Feb 2000 19:46:18 -0500 (EST) Received: from messaging.inprise.com ([10.186.2.160]) by druid.inprise.com (8.8.8+Sun/8.8.7) with ESMTP id QAA04323 for ; Fri, 11 Feb 2000 16:38:01 -0800 (PST) Received: from gkesler2 ([172.20.80.189]) by messaging.inprise.com (Netscape Messaging Server 3.61) with SMTP id AAA4A14 for ; Fri, 11 Feb 2000 16:42:17 -0800 Message-ID: <000701bf74f2$2a62f820$bd5014ac@gkesler2.sm.inprise.com> From: "Gregory Kesler" To: Subject: Need clarification on custructor(s) for stream-based stubs/skeletons Date: Fri, 11 Feb 2000 16:43:18 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01BF74AF.19C31F60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In OMG IDL to Java Language Mapping spec, $1.21.51 "Stub/Skeleton Architecture" there are examples of stream- and DSI- based stubs/skeletons. These examples do not provide any constructors (this mean thay have only default ones). But, it seems that signatures of constructors should be clarified, because orb vendors have a freedom in defining these signatures. For example, the VisiBroker's 4.0 idl2java compiler generates stubs that have only default constructors, but in jdk 1.2 there stubs that have only constructors that take org.omg.CORBA.portable.Delegate as a single parameter. This leads to impossibility for generated stubs to extend the jdk 1.2 provided ones. Thanks. Gregory. [] vijayn.vcf