Synchronizing Stereotypes does not work in 907

[skylord88]

when adding custom tags to a stereotype using a profile + own built MDG the "synchronize" stereotype does not work anymore "older classes having the same stereotypes created in EA 8 in the past are not updated, newly created classes with the stereotypes work fine... any suggestions?

[qwerty]

Report  a bug...

I had a strange behavior with tags yesterday. One tag of a package appeared for an element of the package (I was able to proof that it was the identical tag). Somehow I "rectified" the situation but it seems obvious that Sparxians have mangled the code for Tagged Values somehow....

q.

[shirleyj]

hi,
I also encounterd the same problem.
I sent sparx a bug report with an example of the issue.
they said its being investigated.
hope to see a solution soon.
meanwhile, the way i found to solve this, is to change the stereotypes of the elements you want to sync to something else, and then change it back to the original stereotype. then try to sync again.  it should work now.

[fwoolz]

Synchronization of stereotypes just plain doesn't work in EA 9. As an example, try importing (via .CSV import) several Requirements elements with the stereotype "requirement" and then try to sync with SysML 1.2 Requirements - nothing happens. The reason for this is that the stereotype "requirement" is created as a new stereotype with its own GUID; it thus has no relationship to the corresponding SysML 1.2 stereotype of the same name. The only way to get sync to work is to hack the underlying database (table t_xref) and eliminate the GUID, replacing it with "FQName=SysML1.2::requirement;". Once this is done, sync will work (I've tried it).

Sparx needs to (finally!) break with stereotypes as text strings and recognize them as full-fledged objects. This would include allowing a stereotype to be specified by its FQName and having EA recognize the qualifier as a qualifier, not just part of a meaningless string.

[Eve]

Fred, what you are seeing is that EA isn't synchronizing a stereotype that doesn't actually match the SysML1.2 profile.

In other words, it's working correctly.

[fwoolz]

Simon,

Perhaps, but this leaves those of us who would like to import SysML 1.2 requirements into EA via CSV import up a creek w/o a paddle. Since it is not currently possible to specify an FQName when importing, one is left with the database hack I described. It would be wunnaful if Sparx could revise stereotypes so that an FQName (e.g. SysML1.2::requirements) is correctly parsed, whether typed in or imported, and mapped to the correct profile.

Cheers,
Fred

[qwerty]

I fully agree with Fred's statement.

q.

[Dave_Bullet]

Yup - sync'ing stereotypes with tagged values is completely broken in 906 (either via rightclick toolbox on the type or via the resources view).  My example is on a custom UML profile I created (no MDG / vendor technology involved).  Worked before on 8.0.863