|Re: Different Validation for a model [message #1707411 is a reply to message #1707402]
||Fri, 04 September 2015 14:36
| Ed Willink
Registered: July 2009
You will get on much better by following the up-to-date material in the
The wiki is a valiant effort in 2008 to make sense of a seriously
prehistoric approach. I did some minor repair work in 2012 to refer to
the OCLinEcore editor.
But this is not the way to go. See my reply on the OCL newsgroup.
On 04/09/2015 14:29, Hauke Fuhrmann wrote:
> I found a recipe for my use case in the Eclipse wiki. Very glad for that.
> I follow this recipe to connect my custom Ecore file with my custom
> ocl-File: http://wiki.eclipse.org/EMF/Validation/Recipes
> However, the recipe suggests to reuse some example projects which
> results in having three additional projects with 9 Java classes and a
> lot of plugin.xml config (e.g. editorActions) to glue everything
> together. This is quite some unexpected overhead boilerplate code from
> my point of view.
> Is this really the way to use an CompleteOCL file?
> Any opinion appreciated.
> Am 04.09.2015 09:07, schrieb Hauke Fuhrmann:
>> Hi Ed,
>> thanks for pointing to OCL. I wrote a Complete OCL file now, which
>> worked fine for my model. However, I do not find much information how to
>> connect the ecore with the OCL file. I.e. I want to express that the
>> usual EMF validation should delegate to this OCL validation using my OCL
>> Did not find any extension point for that.
>> The documentation only briefly describes
>> "The CompleteOCLEObjectValidator is used to enable Complete OCL
>> documents to participate in the validation processing of an Xtext
>> The APIs for merging Complete OCL and Ecore as intermediate Pivots and
>> then migrating the Pivot back to Ecore are experimental."
>> As I have no Xtext model but a plain ecore file, I'm a little lost how
>> to actually connect the things such that the validation can be used from
>> the usual ecore-tree-editor and pop up in the problem view.
>> Any hints where to look?
Powered by FUDForum
. Page generated in 0.02080 seconds