Issue 1078:  Association interface generation templates require exceptions (mof-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: For IDL generation, the Association Template needs
 exceptions in the raises clause of some operations.  Compare
 to the generic equivalent, RefAssociation.  For instance,
 what if a null is passed in for a query or update?
 

Resolution: closed issue
Revised Text: 
Actions taken:
March 18, 1998: received issue
July 23, 1999: closed issue
Discussion: 
Response: Section 7.3.6 should be revised to raise the StructuralError exception on the op-eration
"exists" and the operations "with_*" so that null object-reference parameter values
can be reported as ObjectInvalid (see Section 5.3.3). There is no need to add this exception
to the other query operations on this interface ecause they don't have any parameters that
could be structurally malformed. There is also no need to add this exception to the update
operations on this interface as they already can raise StructuralError.
Resolution. The MOF-RTF meeting in Manchester agreed to the above. To be implemented.
Implementation: Since the resolution of “Issue 1085: Consider a better approach to
generated exceptions (mof-rtf)” has replaced StructuralError with
MofError, the template in Section 5.8.10, “Association Template,”
on page 5-60 and Appendix B.1 “MOF IDL Summary” and
throughout Section 3.5, “MOF Model Associations,” on page 3-71
have been updated so that the "exists" and "with_*" operations now
raise Reflective::MofError. Done [KR]
End of Annotations:=====
Return-Path: <GK.Khalsa@unisys.com>
From: "Khalsa, GK" <GK.Khalsa@unisys.com>
To: issues@omg.org, mof-rtf@omg.org
Subject: MOF-RTF: Association interface generation templates require
excep
	tions
Date: Wed, 18 Mar 1998 13:13:28 -0500

For IDL generation, the Association Template needs
exceptions in the raises clause of some operations.  Compare
to the generic equivalent, RefAssociation.  For instance,
what if a null is passed in for a query or update?