Community
Participate
Working Groups
When importing metaclasses in a profile diagram, a user can modify this metaclass (name, attributes and operations) from the model explorer! This has not to be authorized since the metamodel has to be in read-only access. Steps to reproduce: 1. create a profile diagram 2. import a metaclass (class for example) 3. create a stereotype that extend this metaclass 4. go to the model explorer 5. You can have access to the metaclass through the "base_class" attribute of the stereotype 6. Now you can modify the name, attributes and operations
Corrected for Rename, Paste and Delete actions Done in R5482 on the branch oep.uml.menu merged in 5484 commited on R5485 for oep.modelexplorer (plugin not merged because there is others new classes which are not mine.)
I reassign the bug to C. Letavernier, because he manages the action New Child, ... The Drag & Drop action inside the ModelExplorer should be forbidden for the Metaclass too.
In R5489 : for oep.modelexplorer I duplicated code to remove circular dependency.
In R494, on trunk : for oep.modelexplorer I duplicated code to remove circular dependency.
Minor change in 5581 (in AbstractCommandHandler, to avoid to add NULL in the list of the selected elements) and merged in R5582
Many ways to make changes to meta-classes are not possible any more. However, it is possible to change the name of a meta-class by selecting it in the profile diagram and pressing F2
The F2 use case is still broken. The in-line editor is activated and the transaction is (correctly) rolled back when the rename is completed, but that's not the right user experience. The rename action should not be enabled to begin with.
The F2 use case is fixed with commit 6f33209. Feel free to re-open if any other way to edit a metaclass from the UML Metamodel library turns up.
