Issue 8505: CMOF::Exception class is no longer in MOF2.0                                                                                                                                                            (mof2idl-ftf)
Source: Fraunhofer FOKUS (Mr. Michael Soden, soden@ikv.de soden@fokus.fraunhofer.de)
Nature: Uncategorized Issue
Severity: 
Summary: The current specification assumes the existence of a CMOF::Exception class
which was in the MOF2.0 Core submission document but removed during
finalization. Rule (23) on page 21 still refers to this class.

Resolution: 
Revised Text: Revised Text:
Remove rule(23) from the specification and renumber all following rules.
Changes to the document (except re-numbering): remove rule(23) in section 6.2.10 on page 21:
Rule (23) Every instance of the CMOF::Exception class (defined in CMOFReflection) maps to an IDL exception declaration with identifier format_1 ( <exception name>). If an operation raises this exception (see FTF Note 4), an entry is added to its raises clause

Actions taken:
March 7, 2005: received issue
August 1, 2005: closed issue
Discussion: 
Discussion:
The removal of the CMOF::Exception class has only little impact on the IDL mapping. We can easily remove rule (23) from the specification. Moreover, FTF Note 4 (p. 21) has already pointed out the problem in using this class in MOF.

End of Annotations:=====
ource: Michael Soden, soden@fokus.fraunhofer.de
Summary:
The current specification assumes the existence of a CMOF::Exception class
which was in the MOF2.0 Core submission document but removed during
finalization. Rule (23) on page 21 still refers to this class.
------------------


DANKE!


Gruss Michael



--
=============================
Dipl. Inf. Michael Soden
Fraunhofer FOKUS
Kaiserin-Augusta-Allee 31
10589 Berlin Germany


Fon: +49 30 34637235
Fax: +49 30 34638235
=============================