Bug 521994

Summary: EAttribute declared as non-editable in genmodel is editable via default Sirius properties
Product: [Modeling] Sirius Reporter: William Piers <william.piers>
Component: PropertiesAssignee: Project Inbox <sirius.properties-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: jad, laurent.redor
Version: 4.1.1Keywords: triaged
Target Milestone: ---   
Hardware: PC   
OS: Windows NT   
Whiteboard:
Attachments:
Description Flags
WorkspaceProjects.zip
none
RuntimeProject.zip none

Description William Piers CLA 2017-09-07 09:15:38 EDT 
A String EAttribute is editable via default properties (there is no declaration in any .design, so the default behavior is active) although in the genmodel, the attribute is marked as "Property Type: None" or "Property Type: ReadOnly".
This genmodel property affects the generation of .edit.*ItemProvider, especially the getPropertyDescriptors method.
Comment 1 Laurent Redor CLA 2017-10-31 11:43:27 EDT 
Steps to reproduce:
* Import projects from WorkspaceProjects.zip into workspace (metamodel, edit, editor and VSP)
* Launch a runtime
* Import the project SampleInstance from RuntimeProject.zip
* Open the session and the diagram "new MyDiagram"
* In the "Main" section of the Properties section, the "Name" field is OK (writable). But the "Read Only Attribute" is writable too. It should not.
Comment 2 Laurent Redor CLA 2017-10-31 11:44:02 EDT 
Created attachment 271268 [details]
WorkspaceProjects.zip
Comment 3 Laurent Redor CLA 2017-10-31 11:44:17 EDT 
Created attachment 271269 [details]
RuntimeProject.zip
Comment 4 Laurent Redor CLA 2017-10-31 11:45:24 EDT 
For information, the projects for steps to reproduce are made with Sirius 5.1.0 RC4.
Comment 5 Laurent Redor CLA 2017-10-31 11:46:02 EDT 
Thanks for your detailed bug report.
We have reproduced this issue and we consider it as valid.
Nevertheless, it's not yet in the scope of a future release.
Comment 6 Jad El-khoury CLA 2020-05-08 09:00:27 EDT 
The last comment seems to imply that this bug will not be fixed, although the issue is still open. 

So in the hope I can re-ignite interest in solving this bug (which I am currently facing), I thought I add a "+1" to fix this problem.