IBM Support

PK83598: COMPOSITION AGGREGATION SHOULDN'T AFFECT CG:RELATION:ORDERED PROPERTY

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as Permanent restriction.

Error description

  • 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),
    

Local fix

  • No Known Workaround
    

Problem summary

  • When type of relation is changed to Shared or Composition,
    relation changes from Unordered to Ordered.
    

Problem conclusion

  • 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.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK83598

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    740

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-30

  • Closed date

    2010-04-12

  • Last modified date

    2010-04-12

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Document information

More support for: Rational Rhapsody

Software version: 7.4

Reference #: PK83598

Modified date: 12 April 2010