Reputation: 2661
I import XMI of a package hierarchy to a local model, and it's successfully imported.
When I import the same XMI to a shared model (Oracle DB), all the sequences and messages in sequence diagrams are deleted.
Any ideas?
Upvotes: 1
Views: 289
Reputation: 11
With Enterprise Architect v.13 I managed to get rid of the trouble; Supposing that your sequences has Lifelines with Instance Classifier set to the Class/Component that you would like to use in our sequence:
I compared the XMI file generated from a Baseline with an XMI generated by clicking on the option "Import/Export" and they have differences... it seems like that the Exported XMI of the Baseline contains full information of the model (included root nodes), thus I think the import process might resolve each link to objects that are not hold in the same package...
Upvotes: 1
Reputation: 10504
An XMI representation of a model contains information on the elements in the exported package, and their connectors. Structurally, however, the connectors are not stored within the package in EA's data model, so EA simply writes into the XMI file every connector that connects any of the elements to anything else, whether or not the element at the other end of the connector is in scope.
On the other hand, a connector is by definition connected at both ends -- you cannot create a connector in EA that is only connected to an element at one end. This means that each connector is written to the XMI file with a reference to both its elements.
If both elements are in the scope of the XMI export (in the same package tree), then all's well. But if only one of them is, EA is not able to recreate the connector on import -- only one element is present in the XMI file. When this occurs, EA will ignore the offending connector.
The exception to this is if the element which is missing from the XMI file happens to be in the model already. In that case, EA will recreate the connector. I think this might be what you're seeing in your "local" model.
Upvotes: 1
Reputation: 13784
That is a known issue. (search "version control" + "sequence diagram" in the EA forum)
Using instances instead of classifiers in sequence diagrams will to some degree solve that issue.
Upvotes: 1