Tagged value default is applied wrong

[Geert Bellekens]

Details:
I'm working on a UML profile that has a stereotype redefining ArchiMate3::ApplicationComponent
In this stereotype I have added a tagged value named "Domain" with no default value.

In the model I'm using the MDG in (not in the development model) I have a tagged value type definition for a tag with the name "Domain" as well, specified like this:

Type=String;
AppliesTo=UseCase;
Default=CMS;

Now when I create a new element with my stereotype, the default of the model tagged value is applied to my MDG tagged value, so they all get "CMS" as default value.


Steps to Reproduce:
- create a model tagged value definition with the same name as an MDG tagged value
- set a default value in the definition
- notice that the default value is applied to the MDG tagged value

Reported

Geert

[qwerty]

I already posted that here. The Tagged Value creates a global definition and not a local one as one (except Sparx) might think.

q.

[Geert Bellekens]

I already posted that here. The Tagged Value creates a global definition and not a local one as one (except Sparx) might think.

q.

I must have missed that.

Too bad, they have made good progress in no longer "guessing" the stereotype, and mixing different profiles that way, but this is clearly an oversight.
If I define a tagged value in my MDG, that is where they should be looking for it's definition and nowhere else. Tagged values types defined elsewhere should not be taken into account in any way.

Geert

[qwerty]

Maybe it get's fixed if you reported it ;-) Anyway that "feature" is in EA ever since, not just in newer versions.

q.

[Paolo F Cantoni]

Hi Geert,

Did you actually get a default value in the DB or did you just see the default in the properties window or dialog?

I'm fighting my own battles about default as you probably know.  The whole thing is self-inconsistent so we have to write automata to achieve consistent results.

Paolo

[Geert Bellekens]

Hi Geert,

Did you actually get a default value in the DB or did you just see the default in the properties window or dialog?

I'm fighting my own battles about default as you probably know.  The whole thing is self-inconsistent so we have to write automata to achieve consistent results.

Paolo

I didn't actually check the database (yet)
I'll do a quick experiment to find out..

Geert

[Geert Bellekens]

In the database the value is null, so it's only in the GUI that I see the default value.

Geert

[Paolo F Cantoni]

In the database the value is null, so it's only in the GUI that I see the default value.

Geert

Yeah,

That's one of my inconsistency defects.  You'll have seen my rants on the various forms of tagged values and how the defaults are treated differently.

Paolo