[Complete OCL] Change OCL file for validation per editor instance? [message #665859] |
Sun, 17 April 2011 06:43  |
Eclipse User |
|
|
|
Hi,
Reading the excellent slides from Ed and Axel at the EclipseCon ( https://www.eclipsecon.org/submissions/2011/view_talk.php?id =2271) I stumbled upon the chapter on external Complete OCL validation for a Xtext editor.
Without digging to deep myself, I was wandering, whether it is possible to change the (Complete) OCL file that is used for validation in a generated Xtext editor per editor instance (instead of registering them in the OCL Model Registry for all instances).
A sample use case would be a statement in the edited model (e.g. in the editor generated for states.ecore in the workshop examples):
--> snip <--
module "simple.states"
validation "states.ocl"
[...]
--> snap <--
Any comments or directions are welcome.
Best regards
Joern
|
|
|
|
Re: [Complete OCL] Change OCL file for validation per editor instance? [message #665876 is a reply to message #665862] |
Sun, 17 April 2011 15:37  |
Eclipse User |
|
|
|
Joern,
also, it's always good to keep in mind that validating the objects contained in the resource(s) you're editor/editing domain is operating on is only the tip of the iceberg. As soon as you have cross-resource references and OCL constraints navigating such references, you may have to validate other resources too.
Should that be the case, you may want to check out the new OCL Impact Analyzer available since Ingido M6 in the OCL Editors and Examples feature. See org.eclipse.ocl.examples.impactanalyzer.ImpactAnalyzerFactor y for a starting point.
Best,
-- Axel
|
|
|
Powered by
FUDForum. Page generated in 0.05916 seconds