Book a Demo

Author Topic: Orphaned stereotype  (Read 3896 times)

Thomas Mercer-Hursh

  • EA User
  • **
  • Posts: 386
  • Karma: +0/-0
  • Computing Integrity
    • View Profile
Orphaned stereotype
« on: February 27, 2008, 05:55:06 am »
In the Project Integrity Check, I can guess what it means by Duplicate Stereotype Information, but what does it mean by Orphaned Stereotype Information?

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Orphaned stereotype
« Reply #1 on: February 27, 2008, 05:58:52 am »
My guess is that either a stereotype (likely not the primary one) got orphaned when the element it applied to was deleted, or that you've got a defined stereotype that apples to nothing (no element or link types).

You might be able to test the latter theory by exporting reference data and importing it into a blank model. You could then see if the error reappeared.

David
No, you can't have it!

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Orphaned stereotype
« Reply #2 on: February 27, 2008, 12:28:36 pm »
Quote
In the Project Integrity Check, I can guess what it means by Duplicate Stereotype Information, but what does it mean by Orphaned Stereotype Information?
Thomas,

I think it means that there is an entry in t_xref which does not match entries n one of the other tables.

As with ALL (certainly most) the Integrity Check reports...

1) You aren't provided with enough information to do anything meaningful about it
2) It's too hard to do anything without detailed knowledge of the internal workings of EA

So, we've adopted the idiom, of always enabling the repair option and repeating until there is NO error left unfixed.

So far, we haven't found a problem with this approach.

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

Thomas Mercer-Hursh

  • EA User
  • **
  • Posts: 386
  • Karma: +0/-0
  • Computing Integrity
    • View Profile
Re: Orphaned stereotype
« Reply #3 on: February 27, 2008, 01:46:35 pm »
Which, however, doesn't help me fix my program, if it is my program that is causing it.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Orphaned stereotype
« Reply #4 on: February 27, 2008, 02:23:26 pm »
Quote
Which, however, doesn't help me fix my program, if it is my program that is causing it.
It may not be... I recently reported an inconsistency bug between primary stereotype on the t_object and the related entires int_xref.  If you search for it, you might be able to check if you're experiencing the same effects.

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

thomas.kilian

  • Guest
Re: Orphaned stereotype
« Reply #5 on: March 27, 2008, 09:23:42 pm »
Yesterday my DB check revealed a number of oddities. Even a msgbox was popping up during the check (something about BOF/EOF; clicked it away). I ran the correction more than twice and eventually the msgbox did no longer pop up. (Still I feel a bit uncomfortable about the listed errors as I don't know what's actually behind each message and EA is talking about backup and serious changes :o). Now what makes me a bit more uncomfortable is that this stereotype message does not go away. Each time I check/repair it's still there. I'd rather like to know what it could mean and what implications I could expect not getting rid of it. Could someone from Sparx please comment?
Edit: I'll probably post a bug report as this looks very strange to me.

« Last Edit: March 27, 2008, 09:25:16 pm by thomas.kilian »

thomas.kilian

  • Guest
Re: Orphaned stereotype
« Reply #6 on: March 31, 2008, 07:43:09 pm »
Got a response from Sparx:
1. Re-Install MDAC. I definitely will not do that. WGA is a PITA and I happily got rid of that.
2. A link to some Delphi support page. I never used Delphi. So does that indicated EA is written with Delphi? However, I skip that info.
3. Save/Reload to another repository via XMI. Okay. I'll try that. Although it will take me an hour or so for export and import of the DB.
Edit:The ex-/import solved the problem. However, it looks suspicious. Don't know why the integrity check does NOT solve the problem. Maybe some data got lost?
« Last Edit: March 31, 2008, 09:04:13 pm by thomas.kilian »