Wrong stereotype identified

[Paolo F Cantoni]

If you have an MDG Stereotype of a given Name and a Global Stereotype of the same name (perhaps even for a different Base Class) even though the global stereotype does NOT appear on the Global Namespace for that Base Class of Element and you select the MDG named stereotype from the appropriate MDG Namespace, EA will (Often - but NOT always) select the Global stereotype and generate a:

Code: [Select]

@STEREO;Name=<name>;GUID=<some GUID>;@ENDSTEREO;entry instead of the correct:

Code: [Select]

@STEREO;Name=<name>;FQName=<fully qualified name (in MDG)>;@ENDSTEREO;in t_xref.

No wonder my MDG shapescript didn't get activated!

This needs to be fixed ASAP before MORE havoc is wrought in our repositories.

Reported,
Paolo

[Paolo F Cantoni]

There seems to be a related bug - the obverse in fact - where EA applies the rendering for an MDGT created stereotype to an element which has only had global stereotypes applied.

Now the question of how to you handle pre-existing stereotype (and their rendering) in the presence of profile based stereotypes is not trivial - but I suspect this this just a bug.

Anyone else seen this (apart from my alpha testers...  )

Paolo

[Paolo F Cantoni]

Still there in V9 Beta 2.

Just got bitten by it again....

Paolo