Community
Participate
Working Groups
Created attachment 276383 [details] screenshots: meta model / misplaced error marker Steps to reproduce 1. Create the simple Ecore model according to the attached screenshot (meta_model.png in the zip). 2. Implement the 'validName' constaint (e.g. the name should not containt the character 'a'). 3. Create a Sirius diagram representation. For the class 'Container' create a node representation and for the reference 'contains' create a relation based edge representation. 4. Create an instance of the Ecore model, play around with instances of 'Container', add 'contains' relations between them and define invalid names for some of the 'Container' instances. 5. Validate the diagram. 6. Repeat steps 4 and 5 until you end up in a situation like in the attached screenshot (error_markers.png in the zip). As you can see, one of the error markers is positioned on a node and the other one is positioned on an edge. I would expect error markers always to be positioned on nodes and never on relation based edges.
Issue marked as confirmed.
See also forum thread https://www.eclipse.org/forums/index.php?t=msg&th=1078861&goto=1736585&
I did not manage to reproduce the issue. I created the metamodel described in the attached screenshot and a VSM containing a ViewValidationRule and a Semantic Validation Rule. SCenario: * import and deploy the project Marker, Marker.edit and Marker.editor * import the MarkerExample project * Start the validation -> OK: for ViewValidationRule, the marker AND the decorators are created on both the node and the edge. -> OK: for Semantic Validation Rule, the marker AND the decorators are created on the node. For Semantic Validation Rule, it is normal that the marker is not displayed on edge because if the Edge.target==Edge.get sourcecode.getTraget, the marker is not created because it is considered as a duplicate.
Created attachment 285412 [details] MarkerPlugins
ok I ended up figuring out that it was about EMF VAlidation and not Sirius VSM Validation rule. I effectively reproduce the issue with the ecoreProject attached project but not with the MarkerPlugin Meta-model I guess there should be some EMF validation rules on the marker meta-model so that I can reproduce with this meta-model. The rules already exist on the ecore meta-model. For example, there is an error if the name of the EClass is null.
Created attachment 285415 [details] ecoreProject
