This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
For multi valued attribute, MOF prescribes that (from MOF docs) ------------------ "The possible aggregation semantics of an Attribute depend on its type: • If an Attribute’s type is expressed as a DataType, it has “non-aggregate” semantics. • If an Attribute’s type is expressed as a Class, it has “composite” semantics. In cases where an Attribute has “composite” semantics, the Class instance which is the value of the Attribute is a component of the Class instance that contains the Attribute, not vice-versa." ------------------ However, it is possible to have non composite multi valued attribute by using a DataType as Alias of the orginal Class: ------------------ "Note – The above description reflects the fact that the Attribute model element does not have an “aggregation” attribute. A Class-valued Attribute with “non-aggregate” semantics is currently expressed by making the Attribute’s type a DataType, where the DataType’s “typeCode” is an object reference type that is linked to the Class via a TypeAlias." ------------------ This is also remarked in the specs for JMI (4.8.10): "If an AliasType that is an alias to an object is used as the type of an attribute, the composition semantics do not apply to that attribute." ------------------ MDR ignores the fact that a multi valued attribute is defined over an Alias and builds the List (or Collection) as org.netbeans.mdr.handlers.AttrListWrapper, which checks the composition and rises a CompositionViolationException if needed. I belive that the right implementation is like when an attribute is a Collection, i.e. a standard List or something like that.
I am closing all reports in category Java/Unsupported as wontfix. These should be dead issues --- if the reported cases are against some live part of the NetBeans IDE please reopen and we can discuss to which category they belong.