Multiple same-name tagged values in stereotype

[Uffe]

Hi metamodellers,


I'm working on a profile with a stereotype where I want a tagged value to have multiplicity [1..*].
So I create an attribute for the tag in the stereotype, fine, works.

But when I use the resulting profile and want to add additional tags with the same name, things break down.

Let's say my profile is name TheProfile, my stereotype TheStereotype and my tag TheTag.

If I create an element of the relevant stereotype, EA presents TheTag

• In the properties dialog, in a tab TheProfile (and not in the Tags tab)
• In the properties window, in an expansion node TheStereotype in the Element tab (and not in the Tags tab).

If I create a new tagged value and call it TheTag, EA presents that

• In the properties dialog, in the Tags tab (and not in the TheProfile tab)
• In the properties window, in the Tags tab (and not in the Element tab).

That's not what I want. I want it alongside the other tagged values defined in the profile. This is just another instance of one of those.
So I now create a new tagged value and call it TheProfile::TheTag. EA presents that

• In the properties dialog, as TheProfile::TheTag in its own expansion node in the TheProfile tab (and not in the Tags tab)
• In the properties window, not at all.

This also is not what I want.

I'm on 15.0.1512, and according to the history, in 1514 there was a UI change to "Display non profile tagged values that contain '::' in their name". No further changes flagged in 15.1.

So is it now possible to do what I want? That is, add additional instances of a tagged value defined in a stereotype and have them displayed alongside their neighbours, just like EA does with non-stereotype-defined tagged values?


/Uffe

[Eve]

It is possible, at least in the current build. Although it's not as easy as I would like and there are a few clauses.

Tagged Value definitions specified in the technology will be an entry in the new tagged value dialog as TheTech::TagName.

Adding that tag will link with the stereotype property if the technology id is the same as the profile name. (Although if it didn't you wouldn't get the definition anyway)

Unless I'm mistaken, it won't work in 15.0 if you have applied a specialization of the stereotyped that defines the property.