Bug 509081 - [RSA] Class diagrams containing Components gets an additional EAnnotation when additional Components are added
Summary: [RSA] Class diagrams containing Components gets an additional EAnnotation whe...
Status: UNCONFIRMED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-12 09:03 EST by Thomas Wiman CLA
Modified: 2017-08-02 13:45 EDT (History)
2 users (show)

See Also:


Attachments
EMX model and the imported dito (3.34 KB, application/x-zip-compressed)
2016-12-12 09:03 EST, Thomas Wiman CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Wiman CLA 2016-12-12 09:03:40 EST
Created attachment 265832 [details]
EMX model and the imported dito

When importing a model from RSA/EMX containing components that are shown in class diagrams, EAnnotations with source "PapyrusCSSForceValue" are automatically added to the graphical shapes of the imported Components whenever additional Components are added using Papyrus GUI after the import. 

This will make the use of EMF compare difficult as it will expose differences on all shapes imported from RSA as soon as more components are added to the same diagram. 

Steps to reproduce:

1. Create a simple EMX-model in RSA with one class diagram showing one Component.
2. Import the model to Papyrus using the RSA/EMX model import feature.

3. Look into the resulting .notation-file. No EAnnotations have been added.

4. Add Another Component to the same class diagram using Papyrus diagram palette and save the model.

5. Look in the .notation file once more. The Child views of the imported Component has got EAnnotations added with source="PapyrusCSSForceValue", key="type" and value="true"

Attached you will find a zip-file that contains the original EMX-file and the imported model after another component has been added using Papyrus GUI.  

This strange behavior might occur for other imported UML-elements on other diagrams as well. I have only tested with components on class diagrams. 

The expected behavior would be that no additional EAnnotations are added after the import has finalized.