Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: Uffe on June 22, 2020, 10:44:46 pm
-
Hello,
I've been trying to create two element stereotypes in different profiles, with «trace» the only permitted connector between them. In the course of my heroic struggles I've come across a pretty massive inconsistency: metaclasses and stereotypes.
If you add a new metaclass to a profile diagram, EA pops the Extend Metaclass dialog. In this, Trace is listed as a Core Connector. So it's a metaclass.
So I should be able to specify "Trace" as the value in a «metarelationship» metaclass tag.
But no -- I have to use a «stereotyped relationship», which has a stereotype tag where I must specify "EAUML::trace". So Trace is a stereotype.
Going back to the Extend Metaclass dialog, trace is actually listed under EAUML in the Stereotypes tab.
So that's Metaclass 1, Stereotype 2. In the same dialog.
My humble suggestion: sort out once and for all which element / connector is actually a metaclass and which is a stereotype, and while you're at it, how about documenting which relationship needs to be specified with a «stereotyped relationship» and which with a «metarelationship»?
/Uffe
-
Hello,
[SNIP]
My humble suggestion: sort out once and for all which element/connector is actually a metaclass and which is a stereotype, and while you're at it, how about documenting which relationship needs to be specified with a «stereotyped relationship» and which with a «metarelationship»?
/Uffe
Wot 'e sed!
Paolo
-
Look at the properties dialog for the type of connector you want to create. If there is a stereotype, then that's what you need to use for the profile constraints.
There may be some weirdness around trace when extending it, but there are exactly zero special cases for handling of what types are in the profile constraints.