Issue 7681: Rule (38):                                                                                                                                                                                              (mof2idl-ftf)
Source: Vanderbilt University (Mr. Jeff Parsons, j.parsons@vanderbilt.edu)
Nature: Uncategorized Issue
Severity: 
Summary: The CCM mapping for an Association specifies the
suffix "Component" for the derived component.
None of the other derived components in the CCM
mapping have this suffix, and it also disagrees
with some example IDL in the document.



Resolution: 
Revised Text: Resolution:
This observation is correct and Rule (38) should be changed accordingly. Moreover, the specification deliberately omits the definition of a home interface, since all components representing associations are reachable over the package interface.
However, there remains still a conflict in rule (40) (package interface), which states that the package's (abstract) interface has an operation to navigate to the (non-existing) Home interface of a contained association. This must be changed accordingly to be able to navigate from the package directly to the association's derived component. The same applies to nested packages, which also have no home interface (they are created together with the root package).
Revised Text:
Change rule (38) on page 30 into:
If an association is mapped to IDL, a component declaration with the name format_1 ( <association identifier> ) is being generated, which declares to support the abstract interface produced by Rule (25).
Change rule (40) on page 33 into:
A package definition in a MOF model is mapped to an IDL abstract interface definition with the name concatenate ( format_1 ( < package identifier> ), "Package" ) . For each contained class an operation is defined within this abstract interface named format_2 ( <class identifier> ) with the return type concatenate ( format_1 ( <class identifier> ), "Home" ). The operations have no parameters and return the corresponding home interfaces for the classes. Furthermore, the package's abstract interface contains operations for each owned package or association with name format_2( <package or association identifier> ). The return type of these operations is the corresponding abstract interface derived for a package or association (see rule (25)).
Change rule (41) on page 33 into:
Furthermore, a component with the name format_1 ( < package identifier> ) is generated supporting the produced abstract interface. If the package is the outermost package (in case of package merge this is the result of the merge), a home definition is produced named concatenate ( format_1 ( < package identifier> ), "Home" ) that manages the component.

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:26:24 -0500 
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MOF2IDL mapping 
Thread-Index: AcSUJd9PS6crC5PzSIC2kXfMSMmJZA== 
From: "Jeff Parsons" <parsons@isis.vanderbilt.edu> 
To: <issues@omg.org> 
X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i86FfO1U010260 


Rule (38):


The CCM mapping for an Association specifies the
suffix "Component" for the derived component.
None of the other derived components in the CCM
mapping have this suffix, and it also disagrees
with some example IDL in the document.


thanks,

Jeff Parsons