Issue 1516:  Description of with_<associationed> operations (mof-rtf)
Source:  (, )
Nature:  Revision
Severity:  Minor
Summary: Summary: The description of the with_<associationname> operations
 in the IDL mapping needs to give more details of the results returned.
 

Resolution: resolved and closed
Revised Text: 
Actions taken:
June 10, 1998: received issue
May 8, 2000: closed issue
Discussion: 
Discussion:
In the case where multiplicity.upper == 1, the result will be either an object reference for
an object of the 'other' association end's type, or a nil object reference. A nil object refer-ence
can be returned in both the [0..1] case, and in the [1..1] case if the package object has
not been validated.
In the case where multiplicity.upper > 1, the result will be a sequence of (possibly zero)
non-nil object references, where thesequence will contain no more than multiplicity.upper
elements, but could contain less than multiplicity.lower if the package object has not been
validated.
[Aside: in the case where multiplicity.upper == 1, it is no problem for with_* to return a
nil object reference, since it is impossible to create a link involving nil. This contrasts with
multi-valued attributes or parameters where nil object references are legal.]
Proposed resolution: update descriptions as above.
Resolution: If the multiplicity is 1..1, then an object reference is returned. If for any reason
there is no reference to return, the Underflow error kind of MofError is raised. For all oth-er
multiplicities, the result will be a sequence (possibly zero) non-nil object references,
where the sequence will contain no more than multiplicity.upper elements, but could con-tain
less than multiplicity.lower (but does not raise the Underflow exception).
Implementation: This is now documented in Section 5.8.10, “Association Template,”
on page 5-60. Note that these operations have been renamed as part
of the resolution of “Issue 1715: Navigability constraint expressed
wrongly (mof-rtf)”. Done [SC]
End of Annotations:=====

Return-Path: <crawley@dstc.edu.au>
To: mof-rtf@omg.org, issues@omg.org
Subject: MOF-RTF issue: description of with_<associationend>
operations
Date: Wed, 10 Jun 1998 13:53:00 +1000
From: Stephen Crawley <crawley@dstc.edu.au>


Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au)
Nature: Editorial
Severity: Minor
Summary: The description of the with_<associationname> operations
in the IDL mapping needs to give more details of the results returned.

Additional Text:

In the case where multiplicity.upper = 1, the result will be either
an object reference for an object of the 'other' association end's
type, or a nil object reference.  A nil object reference can be 
returned in both the [0..1] case, and in the [1..1] case if the
package object has not been validated.

In the case where multiplicity.upper > 1, the result will be a 
sequence of (possibly zero) non-nil object references, where the
sequence will contain no more than multiplicity.upper elements,
but could contain less than multiplicity.lower if the package object
has not been validated.

[Aside: in the case where multiplicity.upper = 1, it is no problem 
for with_* to return a nil object reference, since it is impossible to

create a link involving nil.  This contrasts with multi-valued
attributes
or parameters where nil object references are legal.]