Book a Demo

Author Topic: Getting consistency in MDG "Types"  (Read 2867 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Getting consistency in MDG "Types"
« on: September 15, 2011, 06:31:13 pm »
We created a repository and added thousands of objects.   We LATER created an MDG technology and continued to add objects.

Now, in the Model Search window, when we do a search for objects we get inconsistent results in the Type column.  Suppose stereotype "S1" is a stereotype NOW associated with MDG technology T1.  The name of the type thus created in T1 is (say) T1_S1.  Some objects in the Model search window have Type = T1_S1 and stereotype = S1 and others have Type = Class and stereotype = S1 - as far as we can tell these are the objects created before the T1 MDGT was created and used in the toolbox.
ALL objects have been "FIXED" to ensure the t_xref stereotype entries have the value associated with the MDG T1 (that is, they have an FQName entry that references T1::S1) and consequently will ALL show T1_S1 in the Type slot of properties window for the object.
If one accesses the properties of a non-T1_S1 object and saves it, the Model Search Type changes from Class to T1_S1 - however this DOES NOT persist across EA invocations. >:(

So what I want to know is where is the "secret sauce" that will make all my objects show T1_S1 in the Model Search Type (or is it just another EAUI bug - among SOOOO many). ::)

We have literally thousands of pobjects to fix and manually is not an option.

TIA,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!