Author Topic: Cannot create two toolboxes in custom toolbox (Read 7255 times)

mse · « **on:** October 28, 2015, 02:54:42 am »

In the CLASS Toolbox for example, there are four categories: Class, Class Relationships, Common, and Artifacts. I am trying to create my own categories using my own profile. So far, I can only get the first category to show up. I have a diagram that has one <<metaclass>> ToolboxPage with two stereotypes extending this metaclass: "System Parts" and "Software Parts".

In System Parts of I have a reference to one of my profile stereotypes such as the following:

Package1::SyHwCmp(UML::Component)
Package1::SySwCmp(UML::Component)

in the other stereotype (Software Parts) I have:

Package1::SwCmp(UML::Component)

However, when I export the diagram as a UML profile, the only thing that shows up in the tool box are the following:

- System Parts
  <<>>SwCmp
   SyHwCmp
   SySwCmp
  <<>>System Parts

The <<>> is the symbol for a stereotype. Thus, my categories are being shown as toolbox elements. Do I have something wrong with my structure?

I am trying to get the following:

- System Parts
   SyHwCmp
   SySwCmp
- Software Parts
   SwCmp

KP · « **Reply #1 on:** October 28, 2015, 10:01:01 am »

It's difficult to know what's going wrong without seeing your model. Check that "Software Parts" is owned by the profile package not some other element, it isn't abstract, that the Extends connector is pointing in the right direction... can't think of anything else. If you're still having problems, please send your technology and the EAP file that you created it from (or an XMI export of the toolbox profile package) to support and someone will have a look.

KP · « **Reply #2 on:** October 28, 2015, 04:01:38 pm »

Another thought: It is very easy to save profiles to the wrong file and then wonder why the changes don't take effect when you re-generate your technology. Try opening your profile files/technology file in a text editor and make sure they contain what you think they should contain.

Paolo F Cantoni · « **Reply #3 on:** October 28, 2015, 06:30:10 pm »

Quote

Another thought: It is very easy to save profiles to the wrong file and then wonder why the changes don't take effect when you re-generate your technology. Try opening your profile files/technology file in a text editor and make sure they contain what you think they should contain.

Ask Me how I know...

Paolo

Glassboy · « **Reply #4 on:** October 29, 2015, 07:24:44 am »

Also make sure you haven't forgotten to have your stereotype extend a metaclass, it's amazing how confusing missing one little connector can be when you start creating your diagrams and toolboxes

mse · « **Reply #5 on:** November 02, 2015, 10:43:25 pm »

Now things are working. The key to getting all this to work was saving SEPARATE packages: one for the toolbox, and another for the profile itself. I was saving everything into a single XML. After studying a bit the example MDG that EA Architect creates for you, then I started to understand the dependencies. I also had to be careful with which package I was saving to avoid overwriting a toolbox with a profile, or a profile with a toolbox.

Follow-up question: how do I insert a Expose Interface into my toolbox? I tried this:

UML::ExposeInterface, but that is not correctly resolved.

Geert Bellekens · « **Reply #6 on:** November 02, 2015, 10:46:30 pm »

Check what EA makes of it when extending such an exposed interface meta class.
Then simply use that in your toolbox.

Geert

mse · « **Reply #7 on:** November 02, 2015, 10:55:36 pm »

I can't find the "exposed Interface" metaclass. Does it go by some other name?

Geert Bellekens · « **Reply #8 on:** November 02, 2015, 11:03:06 pm »

They are seperately listed as RequiredInterface and ProvidedInterface

I'm not sure if you can reuse the EA "exposed interface" metaclass.
But you can certainly make one for yourself that extends both Provided and Required.

Geert

mse · « **Reply #9 on:** November 02, 2015, 11:03:43 pm »

I fixed it. I used the following for my attribute name in the toolbox page:

UML::ProvidedInterface

That was enough to show "Expose Interface" in my Toolbox and make it cause a selection of provided/required interfaces. I suppose I could have also used UML::RequiredInterface.

Geert Bellekens · « **Reply #10 on:** November 02, 2015, 11:11:32 pm »

Quote

I fixed it. I used the following for my attribute name in the toolbox page:

UML::ProvidedInterface

That was enough to show "Expose Interface" in my Toolbox and make it cause a selection of provided/required interfaces. I suppose I could have also used UML::RequiredInterface.

Hmm, go figure :-?

Geert

Sparx Systems Forum

News: