Issue 2196: RefAssociation::link_exists() signature inconsistent (mof-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: Summary: The link_exists() declaration in section 5.3.7 is incorrect. It should match the one in the appendix. Resolution: closed resolved Revised Text: Actions taken: November 6, 1998: received issue July 23, 1999: closed issue Discussion: Implementation: Renamed exists in RefAssociation to be link_exists in Section , “In-terface,” on page 6-23 and Section 6.2.4, “Reflective::RefAssocia-tion,” on page 6-25. No changes required in Annex A as it was correct there. Done [KR] End of Annotations:===== Return-Path: 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 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: RefAssociation::link_exists() signature inconsistent Source: DSTC (Douglas Kosovic, douglask@dstc.edu.au) Nature: Editorial Severity: Minor Summary: The link_exists() declaration in section 5.3.7 is incorrect. It should match the one in the appendix. Return-Path: To: mof-rtf@omg.org Subject: Re: Issue 2196: RefAssociation::link_exists() signature inconsistent Date: Thu, 19 Nov 1998 16:08:47 +1000 From: Stephen Crawley I've noticed another inconsistency with exists() / link_exists() operations. When you pass a "link" to RefAssociation::link_exists() where one or both link ends are null object references (for example), the operation can raise Reflective::InvalidLink. When you pass the same "link" to exists() (in a 'specific' interface), the signature does not allow the operation to raise Reflective::InvalidLink. Instead it must return FALSE. My preferred fix would be to add Reflective::InvalidLink to the exists() operation template (7.3.6)