Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317434

Summary: Validation of scenario gives no Warning if Infector refers to non-existing node
Product: [Technology] STEM Reporter: Matthias Filter <matthias.filter>
Component: UIAssignee: James Kaufman <jhkauf>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P4 CC: sedlund
Version: unspecified   
Target Milestone: 1.1.2   
Hardware: All   
OS: All   
Whiteboard:

Description Matthias Filter CLA 2010-06-21 08:56:08 EDT 
If one uses the context menu option "Validate" after selection of a scenario the user gets the information "Validation completed succesful" even though an infector is used that infects a node that is not part of the model anymore. To implement a plausibility check for all scenario details could be useful in that place.
Comment 1 James Kaufman CLA 2010-07-09 18:22:11 EDT 
This is a feature request.
We now have a validation method that checks the hierarchy of models within a scenario -but it does not check every detail or every decorator.
Comment 2 James Kaufman CLA 2010-08-02 19:21:37 EDT 
Per Stefan's investigation, to address this we need to extend the default emf validation action. please see:

http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.emf.doc/references/overview/EMF.html

under EMF Validation Framework Developer Guide -> Tutorials -> Validation Tutorial.

You also need to install the "Eclipse Modeling Framework Data Integrity Framework and Extenders" to do this.

Doing this will add another dependency on the validation framework to STEM too.
Comment 3 Stefan Edlund CLA 2012-01-19 19:06:22 EST 
The error handling added in the 1.2 release fixed this