Issue 7653: Section: 8.2.2;8.2.6                                                                                                                                                                                    (mof2idl-ftf)
Source: Humboldt-Universitaet (Mr. Mario Winkler, )
Nature: Clarification
Severity: Critical
Summary: In Rule (9) it is stated that the created valuetype which inherits from the abstract valuetype MOFState is truncatable. But according to the CORBA Specification it is not allowed to declare a valuetype as truncatable if it is derived from an abstract valuetype. The base type has to be non-abstract.

Resolution: 
Revised Text: Resolution:
This issue is definitely a bug that was overseen in the specification. In conjunction with issue 7639 the simplest solution is to make the MOFState valuetype non-abstract.

The MOFState valuetype is no longer "abstract" as consequence of resolution of issue 7639.

Actions taken:
September 1, 2004: received issue
August 1, 2005: closed issue
Discussion: 


End of Annotations:=====

m: webmaster@omg.org 
Date: 01 Sep 2004 04:59:08 -0400 
To: <issues@omg.org> 
Subject: Issue/Bug Report 



--------------------------------------------------------------------------------

Name: Mario Winkler
Company: IKV++ Technologies AG
mailFrom: winkler@ikv.de
Notification: Yes
Specification: MOF 2.0 IDL Specification
Section: 8.2.2;8.2.6
FormalNumber: ptc/04-07-01
Version: 1.0
RevisionDate: 07/15/04
Page: 13;16
Nature: Clarification
Severity: Critical
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.4) Gecko/20030619 Netscape/7.1 (ax)
Description
In Rule (9) it is stated that the created valuetype which inherits from the abstract valuetype MOFState is truncatable. But according to the CORBA Specification it is not allowed to declare a valuetype as truncatable if it is derived from an abstract valuetype. The base type has to be non-abstract.