Export/import XMI loses Realization links

[mrblack12]

When I do an XMI export from one EAP and import it into another EAP, it looks as though the realization relationships between various objects (e.g. between requirement and business rules) are lost in the process.

Has anyone experienced the same problem and if so, is there a way to prevent this from happening?

Rick
[original message]

[qwerty]

A client in the Dresden area has contacted me regarding exactly this issue. So if you aren't from there it seems as there is a 2nd one having this issue too. However, except for not using sequence diagrams the right way I haven't heard of such anywhere else.

q.
[original message]

[de Faye@localhost Sethor de Faye]

Unfortunately with issue is correct and repeatable.  A fix for that would be a great help :-)

Regards

Stefan
[original message]

[qwerty]

The issue for my client is more specifically that deleted connectors appeared later (magic un-delete).

I might have found one reason: if you have cross package references and delete them you will be asked what to do with the deletions upon check-in ("Missing Cross-References"). The default from EA is to restore the connectors. So if you press Enter and check out the package later (or issue a Get Latest) the deleted connector is back again.

So it's not that connectors get lost. However, I'd be interested in details for the lost connectors.

q.
[original message]

[de Faye@localhost Sethor de Faye]

Hi Thomas,

i think youre issue is the other way around. There are really connectors, which are getting lost.

To Reproduce it, do the following:
Basic:
EAP-File or DBMS-Repository
Actions:
Select a Package and Export it with XMI Export
Import the XMI to another EAP-File (STRIP GUID NOT Selected)
Export it as another xmi-File
Re-import it in the origin package.  (STRIP GUID NOT Selected)


I tried it out right now with EA10 and it assumes to work now 8-) 8-) or has someone the issue also with EA10?
Can someone try it our with EA9.3?

Regards

Stefan

[original message]

[mrblack12]

What I forgot to mention is that this issue occurs using version 7.3. My company is currently thinking of upgarding to version 10 so it would be great if this bug is somehow fixed in version 10!
[original message]

[qwerty]

Stefan,
I ran a quick test on V10 and obviously the connector gets lost. But I guess in this case it's simply a user error. You need the whole model in the 2nd repos. If you have unsolved references - and that is the case if you only import a single page with cross package references - the export is pretty right in not exporting them again. What you are doing is MODIFYING the xmi simply be im-/exporting. Probably you can argue that EA should keep such hanging connectors. But for a fix this would take a big effort in EA's structure. The t_connectors keep only pointers to exiting objects. Only if you resolve these EA is able to export them. This use case is - from EA's perspective - wrong or forbidden. But definitely it's something to keep in mind. Especially if you exchange XMI data with external clients.

q.
[original message]

[StefanPears]

Hi all, sorry for reopening this old thread, but I guess I have the same problem as discussed above.

When I export a "main package" from an oracle database repository (with its packages controlled by subversion) and I import the XMI into an new and empty EAP-file, all connectors are lost. The main package contains classes and their associations, some are in subclasses. There are no associations to elements outside the main package.

Now I marked some connectors with special text strings before exporting them into XMI. When I examine the XMI file I can find them all and the attributes like sourceId, targetId and other Ids did look pretty well. It seems the export file must be OK? The problem might be in the import process?!

We are using EA 9.3.931 and 10.0.1009. Same problem occurs in both versions.

Thanks for help!
Stefan
[original message]

[qwerty]

I remember having heard that. There seems to be a size mismatch in the database fields. EAP is a bit limited. The best is to contact Sparx support directly so they can help you out.

q.
[original message]

[Dermot]

Stefan,
Regarding your second paragraph - have  your tried using the "Create placeholders for missing External References during XMI 1.1/2.1 Import" - see: http://www.sparxsystems.com/enterprise_architect_user_guide/10/projects_and_teams/xmlspecifications.html
This will indicate if any elements are external.
[original message]

[StefanPears]

Yes, I tried "Create placeholders for missing External References during XMI 1.1/2.1 Import" before. This did not help. One reason is, that there are no connectors to "outside" packages. All internal connectors and even recursive associations are lost.

Btw.: I also tried "Recync status with VC provider" because I first expected the Subversion installation to be damaged.

I will contact Sparx support now.

tx!
[original message]

[StefanPears]

Sparx support offered me to examine the XML file but I was not allowed to send files to outside of the company.

With some help of of my collegues I found a connector with a guard condition having a lenght of 256 chars. I shortened it to 255 chars and the problem was solved. @SPARX: please fix this isue.
[original message]

[skiwi]

1) you need to submit a feature request (http://www.sparxsystems.com/support/feature_request.html)
2) you are likely to get a response such as this Unfortunately, it's a restriction of our database schema, which has only been updated for indexes since version 4.0. I wouldn't expect a change any time soon. (http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1393801894/1#1)
[original message]