Problem with XMI Export/Import Lost Relationship Links

[saliaz]

Hello,

I searched the forum with title of this post but could not find a solution to my problem, so expaining issue i am facing and look forward to receive a solution.

We have both .EAP based (for individual team members) and DBMS based (Master Read-Only repository) environments. We are also using Subversion for .EAP based projects. .EAP based projects are created from a Template (Save as) that contains Common components (reused by the modeling projects) package , meta-model package and a sample / reference modelling project. All three packages are separated inside three separate root nodes.

The aim is individual team mambers work on their models locally primarily .EAP based individual projects and once models are finalised after they are merged using XMI import/export mechanism into DBMS based Master project.

Problem:


Package Structure We follow:

Projects --> <ProjectA>
--> Domain Models
      --> Models
--> App Capabilities
     --> Models

• ProjectA contains number of diagrams (re)using new and existing model components from Common Libarary with associated links (dependencies/realisations) etc.
• ProjectA exported as XMI
• Apply User Locks under Package Control on DBMS based projects
• Import using XMI import which creates new ProjectA package under projects root node as expected.
• Imported diagrams lost relationship links (dependencies/realisations) for the existing components reused from the Common Library, however links between newly created local components remains and are not lost
• Check individual components in common library they also appears to have lost lost links.

I hope the steps expalins the problem but if any further queries please let me know.

Thanks
salman

[Uffe]

Hello Salman, and welcome to the forum.


Please note that most of us here are just users, not Sparx employees. So our advice is just that, not official support responses. If you've registered on the site (free with EA license) you can also send support requests to Sparx directly.

That said, if you're using XMI export/import, and some connectors or diagrams in the export refer to elements which are outside of the exported package, and if those elements do not exist in the project you're importing to, those references are lost.

This problem can be alleviated by using Sparx' reusable asset service, which helps keep track of such hidden dependencies.

There is also an older feature called replication, which may be of use depending on the exact setup.

HTH,


/Uffe

[saliaz]

Hello Uffe,

Thanks for taking time to answer my queries. I think you provided a helpful hint related to the referencing elements outside the exported package. That exactly is the scenario i am dealing with.

We have a large common library package with reuseable elements/components which i am (re)using throughout the diagrams. My project package and common library packages are inside two separate root nodes.

When i export 'project' package it obvously does not contain the elements in the common library package but i assume the XMI should hold the links somehow. So when XMI is imported to a target (DBMS) project which already containts those elements referenced in the imported diagrams. the diagrams should retain the relationship links.

I am looking into the RAS now and also going to raise this with the official support as you advised.

Regards

salman

[PeterHeintz]

From my experience you lose the links to those common library package when doing an xmi import/export (exactly what you have mentioned).
Links are somehow stored on both sides of the connection (I belief). When you import your export, there is neither link information in you import file nor in your target repository common library package.
What is the reason why your users have local copied?
If there is no strong reason it is much simpler to work on the master directly by all users (of cause with some kind of coordination).
Instead of using a DBMS as master you could make e.g. Subversion as master. In this case you work in lock/change/commit mode on packages of your choice. This would also remain your package external links but each time you change something you need to perform a checkout/commit ceremony.