AssociationClass - gone the way of the buggy whip?

[Paolo F Cantoni]

The UML AssociationClass is an example of a materialized relationship.

We previously had a number of these defined (as it happens ONLY for Associations).  The MDG had entries such as:

Code: [Select]

<AppliesTo>
<Apply type="AssociationClass">
<Property name="direction" value="Bi-Directional"/>
</Apply>
<Apply type="Association">
<Property name="direction" value="Source -&gt; Destination"/>
</Apply>
</AppliesTo>
We've noticed that such entries in the MDG no longer work for v15ᵦ.  In order to get them to work correctly (appear correctly on Toolbar, be selected and used to link objects - also via QuickLinker) we had to remove the AssociationClass element above; so that it only created an Association.

Should we just remove the entries for AssociationClass?  From experiments we've done, attaching an existing Class vertex to an existing Association Arc as an AssociationClass doesn't require any additional information in the MDG.

TIA,
Paolo

[Paolo F Cantoni]

[BUMP]

[Eve]

In terms of the metamodel quicklinker, both will work if you specify a different _MeaningForwards/_MeaningBackwards for the two metaclasses. The quicklinker won't show duplicate (by the definition that the user can't tell them apart) items.

On the toolbox, have you specified the base uml type?

Profile::Stereotype(UML::Association)
Profile::Stereotype(UML::AssociationClass)

If a stereotype extends multiple metaclasses and the base type isn't specified you'll get a folder icon. In my test I then had to click somewhere in the diagram and select the base type before dragging between the elements I wanted to link.