Problem importing UML Profile

[tweber]

We have created a profile with several stereotypes.  We encounter problems upon importing that profile on top of its previous version.

When that profile is imported, information boxes appear for each of the listed stereotypes in the profile, followed by an 'Internal application error' note.  The profile itself only appears after closing and re-opening EA.

Once EA is re-opened, the profile elements appear in the 'Resources' list, and also in the 'Toolbox'. However, when an element of nearly all of the stereotypes is dragged onto a diagram, the metaclass (i.e., 'Class1') is created, but not an element of that stereotype. (Interestingly, only a couple of the stereotyped elements are correctly created).

When properties are opened and the 'stereotype' drop-down selected, within the ' ... profile' selection itself, only one stereotype is listed.

Need help on how to correctly export the profile and correctly importing the profile.

[qwerty]

What do you mean by "on top of"?

q.

[Helmut Ortmann]

Hi,

in my experiences most issues regarding profiles are just:
- Misspelling
- The Stereotype, Meta Class isn't in the profile package

I'm also using an editor (e.g. XmlNotePad, but other will also do) to inspect the *.xml file. If nothing helps I start with a minimal profile and extending it step by step.

I know it's sometimes frustrating and such errors aren't easy to see.

Kind regards,

Helmut

[Uffe]

Need help on how to correctly export the profile and correctly importing the profile.

In general, don't work with individual profiles. Create an MDG Technology instead, deploy it to a file share and set up the EA clients to load it from there.

/Uffe

[Geert Bellekens]

Need help on how to correctly export the profile and correctly importing the profile.

In general, don't work with individual profiles. Create an MDG Technology instead, deploy it to a file share and set up the EA clients to load it from there.

/Uffe

Alternatively you can also import the MDG to a model.
Depending on the situation that might also be a good solution.

Geert

[tweber]

Actually, we have two models.  One model contains a package with a <<profile>> stereotype on it (it's the one exported as a UML profile), and the other contains a model that utilizes it.  The stereotypes in the model are stereotypes of class, association, and generalization. It's not a complicated profile.  When we import the exported profile into the 'profile' model, things are fine.  When we import the profile into our other 'working' model, we get a series of 'information' notes for each of the stereotyped elements in the profile, followed by the 'internal application error'.  We have a ton of elements in our model, all built using these stereotypes. 

The replies have begged a couple of questions: 
1) Can we recover using the currently built profile?
2) if we move to MDG Technology, what, if any, are the effects on our current model?
3) Where can we find documentation on 'MDG Technology' and profiles?
4) And, the unanswered question... Why did this happen in the first place?

Some additional information.  We're using Oracle for the DB, and a CM tool for check-out/in.

Thanks.

[Geert Bellekens]

Seems to be that you have a seriously corrupted profile/model.

Things to do:
- run Project integrity check on both models and fix all errors
- try again. If still the same problem send the models to Sparx support and ask them to help you out.

All documentation on profiles and MDG technologies is in the help file, and in the learning centre (Alt-F1). It's just sometimes hard to find the correct three in the forest of information.

Geert

[tweber]

Appreciate the reply.  That said, I did find info on creating an MDG Technology file, created one, added the profile to it, and attempted to save it, only to have EA tell me 'Access is denied'.  That's interesting, because I have r/w permissions in the folder within which I attempted the save. 

[Geert Bellekens]

You don't have the MDG file open another program that locks the file?

Geert