Stereotype based on the Table metaclass

[Jayson]

I have created a stereotype called "artifact" that extends the "Table" metaclass.

Everything works hunky dory except that rather than displaying the stereotype as <<artifact>>, it displays it as <<artifact,Table>>.

Whilst this is not a HUGE deal, I have gone to a LOT of trouble to hide some of the gory details from my user base as they are new to the concept of using a modelling repository rather than nasty old Visio.

Can you tell me why this is showing up when all my other stereotypes act normally? And also, how to rectify the problem.

I am using version 9.3.

Thanks in advance

Jays  

[kepNCI]

Jays (or anyone else):

Did you ever figure anything out about this.

I am trying to do the same thing or something similar. I wanted to create a stereotype of a table so that I can use it to display views with defined columns rather than (or addition to) using EA's view stereotype that only displays the definition text. The overall intent was to be able to associate an application's screen control to the source view.column than in turn can be traced back to the underlying database/schema table.column.

So I used the metatype of "table" and a stereotype called "vTable" whose only attributes were:
   _metatype: string = vTable
   icon: string= c:\.....\image.png
and then added it to an existing section of my custom toolbox with the attribute of:
   MDGName::vTable(UML..Table)

I expected that when I drag the vTable object from my toolbox onto my schema diagram, I would see an object with a stereotype of vTable which has a default name of vTable1 with the defined default color/text.

Instead I get:
- correct default color
- correct stereotype name on displayed diagram box, i.e.:
<< vTable >>"
- Correct association to allow defining table column attributes rather than node attributes.
- incorrect default name. I get "Table1" instead of "vTable1"
- incorrect stereotype when displaying properties. get "Table" instead of "vTable"

NOTE: If I change the property's stereotype from Table to vTable, it changes the attributes to normal node attributes rather than Table column definition.  

Karl  

[qwerty]

tl;dr
There is an ellipsis button near the stereotype entry. You can unselect single stereotypes there.

q.

[kepNCI]

Thanks q

Maybe I am not understanding your response.  In my case the issue is not so much as there are two stereotypes associated with the new object, but that the new stereotype that I created is not picking up the attributes of the table stereotype.
If I use the ellipse button and turn off the "table" stereotype, leaving just my "vTable" stereotype, I loose the capability to define table columns (reverts back to typical node attributes).  What I was hoping via the MDG generation was an object with a stereotype of vTable, a default name starting with vTable and maintaining the column definitions like a table stereotype.

Karl

[qwerty]

This <<table>> stereo (IIRC) has some black magic connected in EA's guts. So you will not be able to live without it, I guess.

q.