Import/export of time-aware models

[Uffe]

Hellu,


If I clone a package structure to a new version, and then export the new version as XMI, will the exported XMI include the non-cloned elements from the original version?

Similarly, if I do a CSV export will the non-cloned elements be included?


/Uffe

[Uffe]

I've tested XMI export, which doesn't include the old versions. Most likely the same goes for CSV.

In order for time-aware models to be useful, they need to be fully integrated with other EA functions, like export. There should be a setting which allows you to specify whether exports should be time-aware or not; alternatively there should be a question pop-up when exporting from a cloned version.

Similarly, in the API, a new method Repository.ExportPackageXMITimeAware() should be added, which includes all the non-cloned contents for a time-aware package structure.

/Uffe

[Paolo F Cantoni]

Hi Uffe,

Like you, having delved into TAM, I'm a bit concerned about some of the current functionality (and more particularly, the UI).

However, from my (still limited) knowledge of TAM, the export is working correctly.  The uncloned vertices are (and probably should) NOT part of the versioned folder.  Consequently, the export should be the same as for a non-TAM package.  I thought these days, the export exported "stubs" for the out-of-branch vertices.  If you're saying the stubs are missing, then that's a bug.

The problem (as I see it) with what you are asking is that (as I said above) the uncloned vertices are in a different structure.  If you force EA to export them as part of this structure, you are exporting a corrupted model.  However, that having been said, there may be use cases where such an export is useful.  Can you elaborate on yours?

Paolo