Issue 11416: More wrong references in chapetr 11 (corba-e-ftf) Source: Remedy IT (Mr. Johnny Willemsen, jwillemsen@remedy.nl) Nature: Clarification Severity: Minor Summary: Section 11 starts with the note that 8.3.4.12 is not required for CORBA/e micro (which should be 11.3.4.12). But the consolidated IDL for corba/e micro does mention this method, probably it needs to removed from there. Maybe also add a note about this to 11.3.4.12 Resolution: Upon further discussion, use cases that demonstrated the need for either create_reference or create_reference_with_id in either profile are lacking. (create_reference and create_reference_with_id were developed for use with Servant Managers, mainly). Therefore, both of these operations are removed from the Compact and from the Micro profile. Revised Text: Delete the first bulleted paragraph in Section 11.2.4. Delete sections 11.3.4.11 and 11.3.4.12. Delete create_reference and create_reference_with_id from the IDL in section 11.4.1 (page 193 of ptc/06-08-02). Delete create_reference and create_reference_with_id from the IDL in section 11.4.2 (page 195 of ptc/06-08-02). Delete from the accompanying IDL. Actions taken: September 17, 2007: received issue July 18, 2008: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 17 Sep 2007 07:18:22 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Johnny Willemsen Company: Remedy IT mailFrom: jwillemsen@remedy.nl Notification: Yes Specification: CORBA/e Section: 11.3.4.12 FormalNumber: 06-08-03 Version: - RevisionDate: - Page: 195 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Description Section 11 starts with the note that 8.3.4.12 is not required for CORBA/e micro (which should be 11.3.4.12). But the consolidated IDL for corba/e micro does mention this method, probably it needs to removed from there. Maybe also add a note about this to 11.3.4.12 X-Virus-Scanned: by XS4ALL Virus Scanner X-Spam-Flag: NO X-Spam-Score: -4.355 X-Spam-Level: X-Spam-Status: No, score=-4.355 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.044, BAYES_00=-2.599] From: "Johnny Willemsen" To: "'Victor Giddings'" , Subject: RE: Straw Poll: issues 10598, 10599, 11416 Date: Thu, 7 Feb 2008 20:21:53 +0100 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acho+VmizX1a7tQUTTOrSePzmntZFgAxE6lw X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m17JNg3K029989 Hi, > 10598: Title: "The use of Full Services definitions in CORBA/e spec". The issue is whether the "Lightweight" version of the the Naming and Event Services should be the basis of services in the Compact Profile. The present spec has the "full" service as required. I see two alternatives: A) Close, No Change or B) adopt basically as specified. Please vote: [A, B, or propose a different solution]: JW: To my idea we should make the change, "lightweight" is the basis 10599: Title: "The removal of static any from micro". The proposal is to include type Any in Micro profile "as an optional compliance point that is not mandatory but is part of the profile". I see three alternatives: A) Close, No Change, B) adopt as specified, C) require type Any support in Micro profile. Please vote: [A, B, or C, or propose a different solution]: JW: This one is harder to answer. I do see that some environment would like to use the Any but on the other side the Any is huge. It could be made an optional compliance point if people think this is really usefull. Just for your info, TAO has Any in its micro profile, we haven't found time to refactor our code 11416: Title: "More wrong references in chapter 11". The issues with the reference numbering somewhat obscures whether create_reference_with_id belongs in CORBA/e Micro profile. I think we should discuss whether the "create_reference" operations are appropriate in either profile. I think it is clear that the ability to create a reference from other than an activated servant was mainly to support ServantManagers and default servants. While it is possible to use create_reference_with_id even with SYSTEM_ID policy, it could be considered unnecessary fluff that gums up the API. I think it is also reasonable to question whether we need these operation in Compact profile. I am more uncertain about the choices for resolving this issue, but lets try A) close, No Change, B) adopt as specified (remove create_reference_with_id from Micro profile), or C) remove create_reference and create_reference_with_id from both Compact and Micro. Please vote: [A, B, or C, or propose a different solution]: JT: I would at least go for removing create_reference_with_id from micro profile. I am not sure whether we should zap this from compact, you are right about the fact that servant manager/default servants are not part of compact also. We could remove it, but I wonder what others have to say. Johnny