Issue 9162: Align CCM Reflection Mapping to MOF2.0 Core                                                                                                                                                             (mof2idl-ftf)
Source: Fraunhofer FOKUS (Mr. Michael Soden, soden@ikv.de soden@fokus.fraunhofer.de)
Nature: Uncategorized Issue
Severity: 
Summary: I suggest the introduction of a RefCCMPackage for CCMreflection Mapping. It is more natural and intuitive for package components to provide RefCCMPackage facets rather than RefCCMBaseObject. The RefCCMPackage should inherit from the RefCCMBaseObject. This could also ease the migration of reflective clients from CCM to Base-IDL Repository
Moreover rule (42) and example (10) use the word support to describe the relationship between concrete home interfaces and RefCCMHome. A home rather inherits from another home. 
Section 8.3.2 uses a RefComponent type not explained anywhere. This should be RefCCMObject, since this guarantees that the concrete object in it is a component.

Resolution: 
Revised Text: Declare the following in the EMOF::CCMReflective and CMOF::CCMReflective modules:
abstract interface RefCCMPackage : RefCCMBaseObject{
} 
Done
Adapt example (10) to
Home AHome : CMOF::CCMReflective::RefCCMHome manages A{
//…
}
and 
Home MyPackageHome : CMOF::CCMReflective::RefCCMHome manages MyPackage{
//…
}
Done
Change RefComponent to RefCCMObject.
Done
In section 8.3.2
RefCCMObject create ( in RefArgumentSetIterator arguments );
was changed to 
RefCCMObject create ( in RefArgumentSet arguments );
In section 
RefCCMBaseObjectBagIterator ref_invoke ( in Operation operation, in ArgumentSetIterator 
arguments );
was changed to
any ref_invoke ( in Operation operation, in RefArgumentSet
arguments );
and the statement
For this method an iterator is defined as follow:
typedef sequence < RefCCMBaseObject > RefCCMBaseObjectSet;
interface RefCCMBaseObjectSetIterator : IteratorBase;
was deleted.

Actions taken:
November 15, 2005: received issue
March 8, 2006: closed issue
Discussion: 

End of Annotations:=====
s is issue # 9162

Align CCM Reflection Mapping to MOF2.0 Core

Michael Soden, soden@ikv.de
Summary:
I suggest the introduction of a RefCCMPackage for CCMreflection Mapping. It is more natural and intuitive for package components to provide RefCCMPackage facets rather than RefCCMBaseObject. The RefCCMPackage should inherit from the RefCCMBaseObject. This could also ease the migration of reflective clients from CCM to Base-IDL Repository
Moreover rule (42) and example (10) use the word support to describe the relationship between concrete home interfaces and RefCCMHome. A home rather inherits from another home. 
Section 8.3.2 uses a RefComponent type not explained anywhere. This should be RefCCMObject, since this guarantees that the concrete object in it is a component.
Discussion:
 
Resolution:
Declare the following in the EMOF::CCMReflective and CMOF::CCMReflective modules:
abstract interface RefCCMPackage : RefCCMBaseObject{
} 
Done
Adapt example (10) to
Home AHome : CMOF::CCMReflective::RefCCMHome manages A{
//.
}
and 
Home MyPackageHome : CMOF::CCMReflective::RefCCMHome manages MyPackage{
//.
}
Done
Change RefComponent to RefCCMObject.
Done
In section 8.3.2
RefCCMObject create ( in RefArgumentSetIterator arguments );
was changed to 
RefCCMObject create ( in RefArgumentSet arguments );
In section 
RefCCMBaseObjectBagIterator ref_invoke ( in Operation operation, in ArgumentSetIterator 
arguments );
was changed to
any ref_invoke ( in Operation operation, in RefArgumentSet
arguments );
and the statement
For this method an iterator is defined as follow:
typedef sequence < RefCCMBaseObject > RefCCMBaseObjectSet;
interface RefCCMBaseObjectSetIterator : IteratorBase;
was deleted.