Issue 1779:  exceptions for resolve_qualified_name() (mof-rtf)
Source:  (, )
Nature:  Revision
Severity:  Minor
Summary: Summary: I think we should reconsider the exception(s) raised by
 NameSpace::resolve_qualified_name().  Firstly, it is not necessary
 to return the resolved part and the name that gave problems as two
 parameters.  Secondly, the exception does not cover the case where
 one of the ModelElements on the path was not a Namespace.
 
 

Resolution: resolved, issue closed
Revised Text: 
Actions taken:
August 6, 1998: received issue
July 23, 1999: closed issue
Discussion: 
Discussion: (crawley@dstc.edu.au)
In the absence of better ideas, I suggest that we follow the pattern of the CosNaming::Not-Found
exception with the tightened up semantics defined by the DSTC et al extended name
service submission. (We can't directly reuse the CosNaming exception because the base
types are wrong for our purposes.)
Status: no progress
Washington - Resolved : Exceptions parallel to how COS::Naming does will be considered.
Reviewed the new Interoperable Naming spec and determined that there are 4 possible
kinds of failure. In keeping with the philosophy of not creating too many exceptions, these
can all be returned by the existing exception NameNotResolved with different parameteri-sation.
Implementation: Revised Section 3.7, “MOF Model Exceptions,” on page 3-92 so
that the NameNotResolved exception now has two parameters: ex-planation
(string) and restOfName (ordered not-unique 0..* of
NameType). The explanation can be "InvalidName", "Missing-Name",
"NotNameSpace" or "CannotProceed" and the first name of
restOfName is the name that could not be resolved satisfactorily.
Revised Section 3.4.2, “Namespace,” on page 3-22 to update the
IDL for the NameNotResolved exception. Revised the MODL in
Appendix C.1 “MODL Description of the MOF”for NameNotRe-solved
and the IDL in Appendix B.1 “MOF IDL Summary”. Done.
[KR]
End of Annotations:=====
Return-Path: <crawley@dstc.edu.au>
To: mof-rtf@omg.org, issues@omg.org
Subject: exceptions for resolve_qualified_name()
Date: Thu, 06 Aug 1998 15:02:07 +1000
From: Stephen Crawley <crawley@dstc.edu.au>


Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au)
Nature: Editorial
Severity: Minor
Summary: I think we should reconsider the exception(s) raised by
NameSpace::resolve_qualified_name().  Firstly, it is not necessary
to return the resolved part and the name that gave problems as two
parameters.  Secondly, the exception does not cover the case where
one of the ModelElements on the path was not a Namespace.

Additional text:

In the absence of better suggestions, I suggest that we follow the
pattern of the CosNaming::NotFound exception ... with the tightened
up semantics defined by the DSTC extended name service team.  (We
can't directly reuse the CosNaming exception because the base types
are wrong for our purposes.)