Problem - xmi import class not showing..

[speekna]

I did an xmi export of a small class diagram from eap model 1 - then imported it into eap model 2.

The project browser in eap 2 shows eap 1's domain model, but the eap 1's classes do not show anywhere in the eap 2's browser.

I can copy a class from the imported eap 1 domain model into eap 2's domain model - everything copies visually - but the class still does not show up in the browser.

If I highlight one of the imported classes on the diagram, and do a "find in browser", EA finds another class - not the one I highlighted.

Any ideas?

[Paolo F Cantoni]

Check that you used the same XMI specifications for both export and import.

If you search for some postings from Darren.Sampson you'll see there are problems with multi-package/multi-model import/export, but your example doesn't appear to be one of those.

If you used XMI 1.3 then try switching to XMI 2.1 (or vice versa).

HTH,
Paolo

[speekna]

I exported using xmi 1.3 last time - i did it using 2.1 this time.  I also chose NOT to import the domain model as a root - but put it under the existing domain model.

This worked.

However, re the suggestion that I specify the same XMI version on input - the window that opened when I chose project >import/export>import project from xmi did NOT have a place for choosing which xmi version to use.

comments welcome.

Also, there are cautions in the user guide regarding xmi, and the fact that not all elements of a model will be represented in an xmi model.  It suggests using tagged values - and it's unclear what that means, in terms of doing an import/export using tags.  Here's the confusing text:

While XMI is a valuable means of specifying a UML model in a common format, it is relatively limited in the amount of additional information it will tolerate using the standard syntax. A lot of information from an EA Model must be converted to what are called 'Tagged Values' - which will import into other modeling systems as additional information or be ignored completely.

EA can both generate and read XMI 1.0, 1.1 and 1.2, using UML 1.3 format and XMI 2.1, using UML 2.0 and UML 2.1 format. Note that round tripping model elements using XMI (for example to version control or for controlled package) is only possible using XMI 1.1/UML 1.3 - EA format which uses the additional tagged values to store the UML 2.0 information.

If somebody could explain (Paolo?) what this means I'd appreciate it...

Thanks very much - the model merge capability still has us experimenting & hoping that we can get something to work so our productivity is at least equivalent to what it is with ERwin...

[Eve]

Hi speekna,

The problem is that you imported the package (which previously was a view) as a root node.  This meant that a root node was directly containing diagrams and elements.  This should never actually occur, and the EA project view doesn't handle it.

[Paolo F Cantoni]

[size=13][SNIP][/size]
Also, there are cautions in the user guide regarding XMI, and the fact that not all elements of a model will be represented in an XMI model.  It suggests using tagged values - and it's unclear what that means, in terms of doing an import/export using tags.  Here's the confusing text:

While XMI is a valuable means of specifying a UML model in a common format, it is relatively limited in the amount of additional information it will tolerate using the standard syntax. A lot of information from an EA Model must be converted to what are called 'Tagged Values' - which will import into other modeling systems as additional information or be ignored completely.

EA can both generate and read XMI 1.0, 1.1 and 1.2, using UML 1.3 format and XMI 2.1, using UML 2.0 and UML 2.1 format. Note that round tripping model elements using XMI (for example to version control or for controlled package) is only possible using XMI 1.1/UML 1.3 - EA format which uses the additional tagged values to store the UML 2.0 information.

If somebody could explain (Paolo?) what this means I'd appreciate it...
[size=13][SNIP][/size]

Well speekna, it should really be up to the Sparxians to reply, but they are pretty busy with the new release (EA 6.5(800.)).  

However, since you asked here's what I understand...

1) That comment may now be out of date - Sparxians should confirm

2) We have configured our packages to use UML/XMI type: Enterprise Architect XMI 2.1/UML 2.1  and don't appear to be having problems.  However, which version it actually uses is moot as we are not certain that the settings that are configured are actually displayed on the dialog during the actual export. - Sparxians should confirm

HTH,
Paolo