Issue 7682: Rule (35): (mof2idl-ftf) Source: Vanderbilt University (Mr. Jeff Parsons, j.parsons@vanderbilt.edu) Nature: Uncategorized Issue Severity: Summary: The home factory operation 'create_<class identifier>' has the same signature as the 'create' operation defined by the CCM spec in the implied-IDL <class identifier>HomeImplicit interface, and for this reason it seems redundant. Resolution: Revised Text: Resolution: Indeed, the default create operation is redundant with the CCM specification's implicit create operation (except that it has a different name). We can omit the generation of the default create operation since it exists implicitly. Revised Text: Change the specification document as follows: Adapt rule (35) in section 6.3.1 on page 26 to: If the class in the model is not abstract, a home interface declaration for the component with the name concatenate ( format_1 ( <class identifier> ), "Home" ) is being generated, managing the component generated following Rule (33). Change the example (3) IDL accordingly (also page 26): module MyPackage { // Common Mapping: abstract interface MyClassCommon : MOFObject { }; valuetype MyClassState : truncatable MOFState supports MyClassCommon { }; // CCM Mapping: component MyClass supports MyClassCommon { attribute MyClassState my_class_state; }; home MyClassHome manages MyClass { }; }; Actions taken: September 6, 2004: received issue August 1, 2005: closed issue Discussion: End of Annotations:===== ubject: MOF2IDL mapping Date: Mon, 6 Sep 2004 10:31:30 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MOF2IDL mapping Thread-Index: AcSUJpVfDkxiEbEXRHSQ+Ea+EJkxag== From: "Jeff Parsons" To: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i86FkU1U010311 Rule (35): The home factory operation 'create_' has the same signature as the 'create' operation defined by the CCM spec in the implied-IDL HomeImplicit interface, and for this reason it seems redundant. thanks, Jeff Parsons