Abstract stereotype and flag and customization

[Thomas Mercer-Hursh]

In the settings for a Class, there is both a check box for abstract (which changes the name to italics, good) and a stereotype for abstract (which puts «abstract» at the top of the box, not so good, but possibly acceptable).  However, if one looks under UML Settings, there is no listing for abstract and thus no ability to do something like change the color.  If one adds a new stereotype abstract with a base of class and sets a non-default color for fill, then the stereotype combo in the class dialog has two entries for abstract, neither of which have the alternate color.

[Geert Bellekens]

The problem seems to be that the "abstract" stereotype is already defined by EA (for some strange reason).
I'm not sure if you can remove the standard abstract stereotype and thus create your own from scratch.

Geert

[Paolo F Cantoni]

The problem seems to be that the "abstract" stereotype is already defined by EA (for some strange reason).
I'm not sure if you can remove the standard abstract stereotype and thus create your own from scratch.

Geert

I DON'T have abstract on the list of stereotypes.  Is it a keyword?

Having spent literally weeks trying to sort out some issues with MDGTs, stereotype and shape scripts, things can get very confusing very quickly.

Start with a base project from Sparx and confirm that the abstract stereotype is there - it's NOT in my 856 base...

If it's not in your base, then it got into your repository somehow...

Create a new class and assign the stereotype to it and then look at the t_xref entry for the stereotype.  That should indicate its source.

HTH,
Paolo

[Geert Bellekens]

No, you are right, I don't have it in my model either.
So either it comes with one of the mdg's, or it was manually added in the model.

I've checked the UML and an alternative presentation option for classifiers is to show the keyword {abstract} after or below the name of the classifier.

Because EA doesn't really make the distinction between keyword and stereotype that might be the reason for this issue.

Geert

[Thomas Mercer-Hursh]

One of the things which is confusing is, for me anyway, it *is* on the list in the combo box of a class, but is *not* on the list under Stereotypes where one modifies the appearance.

[Paolo F Cantoni]

One of the things which is confusing is, for me anyway, it *is* on the list in the combo box of a class, but is *not* on the list under Stereotypes where one modifies the appearance.

Hi Thomas,

For me, not only is it NOT on the list of (global) stereotypes, but it's also NOT in any of the Stereotype namespaces attached to the base.

What is the list of MDGTs you have active?

Did you check what t_xref says?  What does it say?

HTH,
Paolo

[Thomas Mercer-Hursh]

The only MDG I own is the Eclipse interface and I haven't done anything with that since moving to 8.  I do have a piece of custom automation in there related to my ABL2UML work, but there is nothing in that related to abstract stereotype (I'm also not sure how it got into v8 since I haven't done anything with it in a while).

[Paolo F Cantoni]

Did you check a new base model - in your environment?  As I said, my new 856 base didn't have it in it...

FWIW, this is what I'd do next...

With an empty base model, create a class and try to assign the stereotype.  Then I'd check the created t_xref to see if it told me where it came from.  I'd also check if the stereotype had been added to the (global) list.

If it's not clear from the t_xref, then I'd disable the technologies and try again.

That should lead you to what is generating the entry.

HTH,
Paolo