Issue 2165:  Tags that parameterize a meta-model mapping (mof-rtf)
Source:  (, )
Nature:  Revision
Severity:  Significant
Summary: Summary: Summary: If we allow Tags to parameterize a meta-model (e.g. IDL) mapping 
 as proposed for issue 1307 (for example), there needs to be a reliable
 way for a client of the mapped interfaces to find that Tags that were 
 in force.  Without this, it cannot reflectively work out what the mapped
 interfaces do.
 
 Additional text:
 
 

Resolution: 
Revised Text: 
Actions taken:
November 4, 1998: received issue
July 23, 1999: closed issue
August 30, 2000: reopened
Discussion: 
Discussion: The least impact fix is to change the text to match the IDL / MODL.
Proposed resolution: Change the text to match the IDL / MODL.
Implementation: Revised the text and IDL in Section 3.4.2, “Namespace,” on
page 3-22 to say that an exception is raised. Done [KR]
Implementation: Also revised text and IDL for lookup_element_extended in
Section 3.4.3, “GeneralizableElement,” on page 3-26. Done[SC]
End of Annotations:=====
Return-Path: <crawley@dstc.edu.au>
To: mof-rtf@omg.org, issues@omg.org
Subject: Namespace::lookup_element raises exception
Date: Wed, 04 Nov 1998 11:49:40 +1000
From: Stephen Crawley <crawley@dstc.edu.au>


Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au)
Nature: Revision
Severity: Minor
Summary: There is a discrepancy between the description for the 
lookup_elements operation on Namespace and the MODL / IDL for
the operation.  The text says that the operation returns "no
element" if it can't find one that matches.  The IDL / MODL
says that the operation raises Namespace.NameNotFound (which
is mapped to Model::NamespaceClass::NameNotFound).

Additional text:
The least impact fix is to change the text to match the IDL / MODL.