|
| Re: CompleteOCL validation step by step [message #761349 is a reply to message #761332] |
Tue, 06 December 2011 10:34  |
 Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
Hi Hauke
A substantial debug/validation control GUI is on the to-do list. See
http://wiki.eclipse.org/MDT/OCL/Debugger for draft ideas. All
contributions welcome.
For now, Topcased adds an OCL Validation Control layer. You might find
that they do what you want or provide something you can work with. But I
don't think they've moved on to the new PIvot model used by the Xtext
editors yet.
Thinking quickly about the underlying technology. Either the standard
validator is used, in which case unwanted constraints must detect that
they're disabled, or a custom validator is used allowing unwanted
constraints to be ignored. Only a custom validator makes sense, so I
suspect that the solution is to have a new standard validator that
recognises a validation control model in which at least individual
constraints can be enabled/disabled, perhaps have their severities
affected, messages reformatted, target objects filtered ...
You might be able to squeeze all this into the existing validation
context map, but I suspect a new tree traversal is the least of the
difficulties.
Regards
Ed Willink
On 06/12/2011 09:55, Hauke Fuhrmann wrote:
> Hi there,
>
> I want to programmatically call CompleteOCL validation on my EMF model
> instances.
> However, I want to have control in my App about which OCL invariants
> from the big OCL file are executed. Is it possible to validate only a
> specific set of invariants?
>
> Rationale: I want to create a big library of constraints and want to
> enable the user to choose only a small subset of them.
>
> Cheers,
> Hauke
|
|
|
Powered by
FUDForum. Page generated in 0.03122 seconds
] 
Search
Help
Register
Login
Home
