Issue 2205:  Specify behaviour of RefObject.is_instance_of(null,...) (mof-rtf)
Source:  (, )
Nature:  Revision
Severity:  Minor
Summary: Summary: It is not clear what should happen if "is_instance_of" is
 invoked with a null "obj_type" argument.  Should it return false?
 Should it raise the CORBA BAD_PARAM system exception?  Should it
 raise Reflective::InvalidDesignator?  [In the latter case, the 
 exception should be added to the operation signature.]
 

Resolution: see below
Revised Text: Resolution: 

Reflective::InvalidDesignator should be raised in this case, and in every other case where a null 'designator' argument is passed.  The current description of the exception pretty much covers this case, but there is no harm in clarifying the wording. 

Revised Text: 

In Table 5-5 in Section 5.5.6, change the "Description" for "Invalid Designator" to read: 

  "Invalid Designator" arises when a "feature" parameter: 

      * is not a Model::ModelElement, or 
      * does not denote an assessible (non nil) CORBA Object. 

The proposed change adds the phrase "... (non nil) ... ". 


Actions taken:
November 12, 1998: received issue
December 3, 2001: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <crawley@dstc.edu.au>
To: mof-rtf@omg.org, issues@omg.org
Subject: specify behaviour of RefObject.is_instance_of(null, ...)
Date: Thu, 12 Nov 1998 13:50:35 +1000
From: Stephen Crawley <crawley@dstc.edu.au>


Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au)
Nature: Revision
Severity: Minor
Summary: It is not clear what should happen if 'is_instance_of' is
invoked with a null 'obj_type' argument.  Should it return false?
Should it raise the CORBA BAD_PARAM system exception?  Should it
raise Reflective::InvalidDesignator?  [In the latter case, the 
exception should be added to the operation signature.]





X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: mof-rtf@omg.org
Subject: Re: Issue 2205: Specify behaviour of
RefObject.is_instance_of(null,...)
Mime-Version: 1.0
Date: Tue, 12 Jun 2001 16:10:49 +1000
From: Stephen Crawley <crawley@dstc.edu.au>
X-Scanned-By: MIMEDefang 1.0
(http://www.roaringpenguin.com/mimedefang/)
Content-Type: text/plain; charset=us-ascii
X-UIDL: Iacd9Dd]d9"Qp!!I43e9


> Nature: Revision 
> Severity: Minor 
> Summary: It is not clear what should happen if "is_instance_of" is
> invoked
> with a null "obj_type" argument. Should it return false?
> Should it raise the CORBA BAD_PARAM system exception? Should it
> raise 
> Reflective::InvalidDesignator? [In the latter case, the exception
> should 
> be added to the operation signature.]

Proposed resolution:

Reflective::InvalidDesignator should be raised in this case, and in
every
other case where a null 'designator' argument is passed.  The current 
description of the exception pretty much covers this case, but there
is
no harm in clarifying the wording.

Proposed Revised Text:

In Table 5-5 in Section 5.5.6, change the "Description" for "Invalid
Designator"
to read:

  "Invalid Designator" arises when a "feature" parameter:

      * is not a Model::ModelElement, or
      * does not denote an assessible (non nil) CORBA Object.

The proposed change adds the phrase "... (non nil) ... ".