Eclipse Community Forums: EMF » EMF Validation

Help

Home

Home » Modeling » EMF » EMF Validation - constraints(constraints)

Show: Today's Messages :: Show Polls :: Message Navigator

EMF Validation - constraints [message #756240]

Fri, 11 November 2011 16:00

adampatrick

Messages: 6
Registered: January 2011

Junior Member

Started to use annotations to define constraints.

Define the first constraint ok on the EClass... EAnnotation >> Details Entry

setting all the properties in the ecore model to the right values

this first constraint is to do there is two attributes min and max and as a quick constraint min cannot be greater than max.... implemented (java - once the code stub created) and tested this and all works ok!

then wanted to set another constraint - having min and max both set at zero does not make a whole lot of sense .....

.... now at first I thought that I should define a new 'Details Entry' in the annotation I defined but doing this causes the ECore model to be invalid.... I called the Key 'constraints' and entered something appropriate in Value. .... error was...."feature details has a map entry at index 1 with a key that collides with that of the map entry at index 0".....hmmmm

then I thought maybe you have to define a seprate annotation for each constraint ... but this then failed to generate any code for this constraint.

So then I thought are you only supposed to define one constraint per EClass (it does not seem right in my head to do this)? but wanted to get some good opionions first before I do that

.... as a side:
may want to define further constraints too on this one EClass .... having negative min/max values does not make sense either.....

Report message to a moderator

Re: EMF Validation - constraints [message #756250 is a reply to message #756240]

Fri, 11 November 2011 16:27

Ed Merks

Messages: 33142
Registered: July 2009

Senior Member

The key is "constraints" (plural) and the value is a space separated
list of named constraints.

On 11/11/2011 5:00 PM, adampatrick wrote:
> Started to use annotations to define constraints.
> Define the first constraint ok on the EClass... EAnnotation >> Details
> Entry
>
> setting all the properties in the ecore model to the right values
>
> this first constraint is to do there is two attributes min and max and
> as a quick constraint min cannot be greater than max.... implemented
> (java - once the code stub created) and tested this and all works ok!
>
>
> then wanted to set another constraint - having min and max both set at
> zero does not make a whole lot of sense .....
> ... now at first I thought that I should define a new 'Details Entry'
> in the annotation I defined but doing this causes the ECore model to
> be invalid.... I called the Key 'constraints' and entered something
> appropriate in Value. .... error was...."feature details has a map
> entry at index 1 with a key that collides with that of the map entry
> at index 0".....hmmmm
>
> then I thought maybe you have to define a seprate annotation for each
> constraint ... but this then failed to generate any code for this
> constraint.
>
> So then I thought are you only supposed to define one constraint per
> EClass (it does not seem right in my head to do this)? but wanted to
> get some good opionions first before I do that
>
> ... as a side:
> may want to define further constraints too on this one EClass ....
> having negative min/max values does not make sense either.....
>
>
>
>
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator