Issue 2193:  Document how to "unset" using the RefObject interface (mof-rtf)
Source:  (, )
Nature:  Revision
Severity:  Minor
Summary: Summary: In cases where there "specific" interfaces unset operation,
 the unset operation can be called using the RefObject::set_value()
 operation, where the ValueType parameter of set_value() is a CORBA
 Any of kind tk_null. This needs to be stated in the spec.
 
 

Resolution: closed, resolved
Revised Text: 
Actions taken:
November 6, 1998: received issue
July 23, 1999: closed issue
Discussion: 
Alternatively, have an "unset_value" in RefObject which raises MofError when the lower
multiplicity is >1. This may be easier for users than building an any with tk_null inside.
Implementation: Ref_unset_value() operation added; .see Section 6.2.3, “Reflec-tive::
RefObject,” on page 6-10. Done. [SC]
End of Annotations:=====
Return-Path: <crawley@dstc.edu.au>
To: mof-rtf@omg.org, issues@omg.org
Subject: Issues with the MOF Reflective interfaces
Date: Sat, 07 Nov 1998 02:04:02 +1000
From: Stephen Crawley <crawley@dstc.edu.au>


This message contains a set of issues that DSTC have discovered while
implementing the MOF Reflective interfaces.  Don't panic.  They are
all "minor" :-)

Credit for finding them and carefully documenting them is due to
Douglas Kosovic.

-- Steve

===================================================================
Subject: Document how to "unset" using the RefObject interface
Source: DSTC (Douglas Kosovic, douglask@dstc.edu.au)
Nature: Revision
Severity: Minor
Summary: In cases where there 'specific' interfaces unset operation,
the unset operation can be called using the RefObject::set_value()
operation, where the ValueType parameter of set_value() is a CORBA
Any of kind tk_null. This needs to be stated in the spec.