Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Papyrus Software Designer/Model Code Synchronization
< Papyrus Software Designer
Revision as of 11:19, 26 October 2016 by Shuai.li.cea.fr (Talk | contribs) (Created page with "= Model Code Synchronization = This page gathers ideas on the model-code synchronization component of Papyrus Software Designer, developed by IncQuery Labs and CEA. It will l...")
Model Code Synchronization
This page gathers ideas on the model-code synchronization component of Papyrus Software Designer, developed by IncQuery Labs and CEA. It will later become a finalized wiki page for users and developers. The synchronization component is based on change-based incremental transformation (code generation and reverse).
UML and Java
Events to handle (both UML side and Java side):
- Addition
- Deletion
- Rename
- Move
- = Addition + Deletion?
- Refactor [UML-side] such as “impact of changing any element E on other elements that reference ”, e.g.
- Impact of a renaming performed on a class which types properties
- Impact of moving some class, typing properties, to another package
- Refactor [Java-side]
- By using the JDT refactor command, referenced JDT elements will be updated, firing change events so no problem.
- Without using JDT refactor command, we will have broken code to be ignored (e.g. attribute with nonexistent type). I don’t think JDT will fire a change event on the broken code.
It doesn’t matter if such events are not explicit, as long as we can express them (e.g. combination of other events) and update elements without ambiguity.