I wanted to change the rendering of an n-Ary Association Lozenge. So I created a stereotype. I looked down the provided list of base classes for the stereotype and found "n-ary association". I selected it made the desired changes and saved the stereotype specification.
The stereotype DIDN'T apply the desired rendering.
Since I'm now well versed in EAUI, I tried my usual technique of getting EA to tell me what it thinks is going on... I changed the stereotype to a nonsensical one in the element itself and then opened the
Settings|UML...|Stereotypes dialog to find out what base class EA had assigned. To my surprise (Not really - since n-ary association hadn't worked), EA had created a stereotype with base class "associationex"
- which isn't on the list!
Now, normally, when you select a globally stereotyped element and then select
Settings|UML...|Stereotypes EA will
conveniently open the dialog at the selected primary stereotype. This time it didn't... (An indication that "there's something crook in Tobruk"!).
OK, so I change the rendering of THIS stereotype -
created by EA itself! - and it still DOESN'T apply!
Eventually, I found that selecting the "association" base class would apply the rendering!
BUT... And this IS where INSULT is added to INJURY! The stereotype doesn't appear in the element's stereotype drop-down
unless the base class is set to "associationex"!
So I have to define one stereotype but have it rendered according to another! :-?
Will EA please make up its mind as to what this Lozenge is? How does Geoffrey Sparks expect his users to figure this out if his own product can't? 
This is reminiscent of the
Realization debacle... See:
Dear Geoffrey...Reported,
Paolo
If you want to vote for a fix for this, submit a Registered Bug Report or Bug Report
with the same name, leaving a note here to say you've done it
- so we users have an indication of the level of support.
