Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Camille save destroys transitions in iUML-B state-machines #27

Open
cfsnook opened this issue Apr 11, 2018 · 3 comments
Open

Camille save destroys transitions in iUML-B state-machines #27

cfsnook opened this issue Apr 11, 2018 · 3 comments

Comments

@cfsnook
Copy link

cfsnook commented Apr 11, 2018

Saving in Camille tries to ignore (i.e. preserve) iUML-B state-machines (even though they appear to have been deleted because there is no text representation). However, a transition's source/target references have an eOpposite relation with States incoming/outgoing references. Only the incoming/outgoing references are preserved; the source/target references are deleted resulting in an invalid model.

Before saving with Camille:
image

After saving a change in Camille:
image

Looking with Rose editor reveals missing properties source and target:
image

The model can be repaired by deleting and re-writing the incoming/outgoing properties of the states. (which automatically updates the source/target properties since they are eOpposite).

N.b. there are other eOpposite relationships in e.g. Class diagrams etc.

@cfsnook
Copy link
Author

cfsnook commented Apr 11, 2018

This is using Camille 3.2, Rodin 3.3, iUML-B Statemachines 3.4.1

@wysiib
Copy link
Contributor

wysiib commented Apr 13, 2018

This might be related to #26. Maybe the eOpposites are the child elements that should not be merged?

@cfsnook
Copy link
Author

cfsnook commented Apr 13, 2018

It might be related somehow.... but I am pretty sure there are no eOpposites used in the Event-B EMF - they are only used when you have iUML-B extensions in the model.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants