Issue 785: IDL Generation Issue - factory operation parameters for multivalued attrib (mof-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Minor Summary: Summary: Multivalued, read-only attributes can never be given more than a single value Resolution: resolved and closed Revised Text: Response: Section 7.3.5 should show the parameter type name as having a CollectionKind suffix (Set, Bag, List, UList) when the attribute is multi-valued. This was agreed by the sub-mitters but not properly documented in the submission. Resolution. The MOF-RTF meeting in Manchester agreed to the above. To be implemented. Implementation: Text added to Section 5.8.9, “Class Create Template,” on page 5-58. Consequentially the values parameter in the create_tag operation must have type AnyBag instead of "any" in TagClass in Appendix B.1 “MOF IDL Summary” and this must be reflected in the text and IDL in Section 3.4.23, “Tag,” on page 3-68. Done [KR]. Actions taken: December 2, 1997: received issue July 23, 1999: closed issue Discussion: received issue End of Annotations:===== Return-Path: Subject: IDL Generation Issue - factory operation parameters for multivalued attributes To: mof-rtf@omg.org Date: Tue, 2 Dec 1997 19:53:48 +0000 (GMT) From: GK Khalsa Reply-to: khalsa@objectrad.com Organization: Object Radiance, Inc. Here's an issue that I'd like the MOF RTF to take up. I don't know if there's any kind of standard format for issues. I borrowed this format from some old OMG issues. Source: Unisys (GK Khalsa, khalsa@objectrad.com) Nature: IDL Generation Rules Severity: Minor Summary: Multivalued, read-only attributes can never be given more than a single value Resolution: Revised Text: Actions taken: Discussion: The rules for generating the factory operation of a MofClass state that a parameter is provided for each attribute of the type of the attribute. For a read-only attribute, this becomes the only time a value can be assigned to the attribute (unless the modeler specifies some explicit operation). This means that a multivalued attribute -- one where the upper cardinality limit is greater than one or unbounded -- can never have more than a single value. Suggest changing the IDL generation rules, so that for each multivalued attribute, the type of the corresponding parameter is a sequence of the attribute type. This sequence should be one of the {Set, Bag, List, UList} typedefed collections. --- GK Khalsa khalsa@objectrad.com Object Radiance, Inc. v: +1 909 677 2518 http://www.objectrad.com f: +1 909 677 1478 Return-Path: To: khalsa@objectrad.com Cc: mof-rtf@omg.org Subject: Re: IDL Generation Issue - factory operation parameters for multivalued attributes Date: Wed, 03 Dec 1997 11:22:14 +1000 From: Kerry Raymond > Discussion: The rules for generating the factory operation > of a MofClass state that a parameter is provided for each > attribute of the type of the attribute. Do you mean "Type Create Template" in Clause 7.3.5? If so, it seems a second RTF issue to get alignment on the names used between the sections of the document. It seems that some of the last minute name changes haven't been propagated throughout the entire document. We seem to have "Class" and "Type" in different parts of the document, and now GK is talking about MofClass. > For a read-only attribute, this becomes the only time a value can be > assigned to the attribute (unless the modeler specifies some > explicit > operation). This means that a multivalued attribute -- one where > the > upper cardinality limit is greater than one or unbounded -- can > never > have more than a single value. Suggest changing the IDL generation > rules, so that for each multivalued attribute, the type of the > corresponding parameter is a sequence of the attribute type. This > sequence should be one of the {Set, Bag, List, UList} typedefed > collections. Yes, this is definitely what is intended. For a multivalued attribute, the template should be . Kerry