PK83598: COMPOSITION AGGREGATION SHOULDN'T AFFECT CG:RELATION:ORDERED PROPERTY
Closed as Permanent restriction.
222974 When using an unbounded relation, setting it to Shared or Composition changes the relation from Unordered to Ordered respectively. The order property shouldn't be affected by the aggregation type. To reproduce: 1. add two classes with a relation between them. 2. set one end of relation to * multiplicity. 3. open code view for classes. 4. change the aggregation to shared (note code shows relation as OMCollection) and then change to composition (note code shows relation as OMList),
No Known Workaround
When type of relation is changed to Shared or Composition, relation changes from Unordered to Ordered.
It's possible to choose the desired container by setting the value of the property CG:Relation:Implementation. In this case, it can be set to UnboundedUnordered.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following: