UML Profile: Stereotyped Package when loaded is actually a Class?!

[David Rains (bioform)]

I am back to using EA in my new job   Starting creating some profiles (stereotyped packages and classes) in 14.1 (last build) and switched to 15...
Problem (tested in 14.1 and 15) is when I extend my stereotype "package" to the package metaclass, and my stereotype "class" to the class metaclass; export/import I get:

- Class Icon represented as Package, but when dragged onto diagram - it IS a stereotyped Class (ok, can live with that... I guess)
- Package Icon represented as Package, but when dragged onto diagram - it IS a stereotyped Class (umm, can't live with that....)

Anyone else experiencing this... Any workarounds... I can live without some of the tagged values on the packages, and such if I have to... and just define the Stereotypes manually...

BTW: Was going to stay in 14 as an add-in I am trying out (OntoUML) works in 14.1 but not in 15. But is it worth jumping into 15 at this time? Might not be a bad time for me (or my client as this will be totally new to them...)


Thanks as always... (this seems to be a common issue with releases if memory serves me...)

David "Back in the EA space" Rains

[qwerty]

I have not tested V15 much (talked about that elsewhere): From what I saw it did not look too bad (that's a word from me!). There seems to have been done quite some rework (and again I feel the direction is much better than what hit me in latter versions. One strong point: the WHere Is my Menu (WHIM) is still manifested in EA releases. If you want to avoid user shocks you should look at both versions and settle for one. I'm pretty sure others with experience in V15 will chip in.

q.

[David Rains (bioform)]

There seems to have been done quite some rework (and again I feel the direction is much better than what hit me in latter versions. One strong point: the WHere Is my Menu (WHIM) is still manifested in EA releases....q.

Yes the UI in v15 does look a bit cleaner and WHIM is always an issue in major releases  
My tagged values in my stereotypes are showing up (as pointed out) with the other properties which is nice.. however my issues seems to be worse than I thought... my stereotyped associations are also being implemented as CLASSES?!!
So right now I am unable to produce working MDGs in v15?!!!  Could someone verify if they are having this issue? <going back to v14.1 and see what happens>

[David Rains (bioform)]

Okay I have verified that my profiles in both 14.1 and 15 create nothing but packages... The XML looks valid to my eyes... (selected parts below)... Not an exhaustive test, but of 7 different element types each of which is NOT a class, they all represent as classes... [going to delete the project and start from scratch...]

<?xml version="1.0" encoding="WINDOWS-1252"?>
-<UMLProfile profiletype="uml2">
<Documentation notes="Party" version="" name="Party" id="3E785814-4"/>
-<Content>
-<Stereotypes>
-<Stereotype notes="" name="memberIn" hideicon="0" borderwidth="-1" bordercolor="-1" fontcolor="-1" bgcolor="-1" cy="70" cx="90">
-<AppliesTo>
-<Apply type="Association">
<Property name="compositionKind" value="none"/>
<Property name="direction" value="Source -> Destination"/>
</Apply>
</AppliesTo>

</Stereotype>
-<Stereotype notes="" name="orgOf" hideicon="0" borderwidth="-1" bordercolor="-1" fontcolor="-1" bgcolor="-1" cy="70" cx="90">
-<AppliesTo>
-<Apply type="Dependency">
<Property name="direction" value="Source -> Destination"/>
</Apply>
</AppliesTo>

</Stereotype>
-<Stereotype notes="" name="MyActor" hideicon="0" borderwidth="-1" bordercolor="-1" fontcolor="-1" bgcolor="-1" cy="70" cx="90">
-<AppliesTo>
<Apply type="Actor"/>
</AppliesTo>
</Stereotype>
....

[KP]

[going to delete the project and start from scratch...]

First, try reloading the project. I assume you imported the profile in the Resources view and are dropping elements from there onto the diagram. I just did that and got the same results as you, but it worked after a reload.

[David Rains (bioform)]

I will try that. It was accepted as a bug, and I am now actually creating an MDG instead (in the past I am not creating profiles for other users, just myself). So I have bit the bullet and have started down that path... Partly implementing OntoUML... (1st attempt without model validation, but with constraints on relationship type connectors against stereotype classes)

Just tried to implement constraints on multiplicity of my stereotyped association using the Add Stereotype | Profile Helper (Who new how easy that was!) - Okay, almost everyone else... I was searching for a list of relationship properties.... and thought hey, I wonder....