Eclipse Community Forums: Epsilon » Best way to realize constraints in meta model

Home » Modeling » Epsilon » Best way to realize constraints in meta model

Best way to realize constraints in meta model [message #1073455]

Wed, 24 July 2013 16:53

Eclipse User

Hi,

I was thinking about the best way to realize a meta model constraint with Eugenia. Imagine the following metamodel:

index.php/fa/15705/0/

I read a little bit about the Epsilon Validation Language, would this be a reasonable way for realsizing this? Or are there better ways?

Cheers,
Phil

Attachment: xor_emf.JPG
(Size: 36.42KB, Downloaded 611 times)

Re: Best way to realize constraints in meta model [message #1073461 is a reply to message #1073455]

Wed, 24 July 2013 17:12

Eclipse User

Hi Phil,

EVL should be fine for this. Off the top of my head, your constraint would look like this:

context Remove {
constraint PropertyXorElement {

check: self.elementToRemove.isDefined() xor self.propToRemove.isDefined()

message: self + " cannot remove both an element and a property"

}
}

Cheers,
Dimitris

Re: Best way to realize constraints in meta model [message #1073703 is a reply to message #1073461]

Thu, 25 July 2013 06:40

Eclipse User

Thx Dimitris,

that's great so far. One of the features of EVL is "Out-of-the-box integration with the EMF validation framework and GMF"..Since I'mn using an combined EMF/GMF Editor and the meta model constraint is only part of the EMF Editor (for this classes, there are no eugenia annotations in the emf file, but I'm still using Eugenia to generate both editors). I'm wondering if EVL also works in the EMF Editor or is just applicable for the gmf editor??

Cheers,
Phil

Re: Best way to realize constraints in meta model [message #1073706 is a reply to message #1073703]

Thu, 25 July 2013 06:44

Eclipse User

Hi Phil,

EVL hooks into the EMF Validation framework so it also works on tree-based EMF editors.

Cheers,
Dimitris

Re: Best way to realize constraints in meta model [message #1073803 is a reply to message #1073706]

Thu, 25 July 2013 10:13

Eclipse User

Ok, I tried this, but the validation doesn't seems to work right. By using this metamodel (only a part)

index.php/fa/15711/0/

and this concrete Model, I get this:

index.php/fa/15712/0/

I used the constraint for the Remove class, which you mentioned earlier Dimitris. Normally the validation should be fine, cause there is no remove class yet. Am i missing something?

Cheers,
Phil

Attachment: validation.JPG
(Size: 40.86KB, Downloaded 596 times)
Attachment: validation_error.JPG
(Size: 55.56KB, Downloaded 586 times)

Re: Best way to realize constraints in meta model [message #1073805 is a reply to message #1073803]

Thu, 25 July 2013 10:18

Eclipse User

Hi Phil,

These errors come from EMF itself as your model doesn't seem to be conforming to the cardinalities specified in its metamodel (e.g. a VariationElement is required to have a Remove, a ConcreteProperty etc as the minimum cardinality of its respective references is 1). To make these errors go away I'd suggest that you set the cardinalities of these references to 0..1 instead.

Cheers,
Dimitris

Re: Best way to realize constraints in meta model [message #1073897 is a reply to message #1073803]

Thu, 25 July 2013 14:08

Eclipse User

You're absolutely right Dimitris.

But the self defined constraint doesn't seems to work, no matter how I define the constraint:

index.php/fa/15714/0/

So I set a BreakingPoint to my evl file and it seems that the constraint definition isn't used.

I followed this article (http://www.eclipse.org/epsilon/doc/articles/evl-gmf-integration/) and not sure about the definition of the extension point, especially the markerType.. As I seen from the article, I think I've to refer to my diagram project, but what is the diagnostic class?

<markerResolutionGenerator
      class="org.eclipse.epsilon.evl.emf.validation.EvlMarkerResolutionGenerator"
      markerType="org.model.variability.diagram.diagnostic">
</markerResolutionGenerator>

Attachment: constraint.JPG
(Size: 36.52KB, Downloaded 549 times)

Re: Best way to realize constraints in meta model [message #1073995 is a reply to message #1073897]

Thu, 25 July 2013 18:52

Eclipse User

Hi Phil,

The class looks correct. Could you please double-check that the namespaceURI in your constraintBinding extension matches that of your root Ecore package? If it does, please send me a copy of your project at epsilon.devs@gmail.com and I'll investigate.

Cheers,
Dimitris

Re: Best way to realize constraints in meta model [message #1074275 is a reply to message #1073995]

Fri, 26 July 2013 08:10

Eclipse User

Hi Dimitris,

my namespaceUri matches my package name,w hcih I've defined in my emf file:

@namespace(
	uri="/org.model.variability/model/pld.ecore",
	prefix="p")

package pld;

<constraintsBinding
            compose="true"
            constraints="validation/Variationpoint.evl"
            namespaceURI="pld">
      </constraintsBinding>

Should be right, or?

But for the markerType, Eclipse metioned the following:

Referenced identifier 'org.model.variability.diagram.diagnostic' in attribute 'markerType' cannot be found

Cheers,
Phil

Re: Best way to realize constraints in meta model [message #1074279 is a reply to message #1074275]

Fri, 26 July 2013 08:17

Eclipse User

Hi Phil,

The namespaceURI should be /org.model.variability/model/pld.ecore (the same as the uri of your package). You can use the browse button next to the markerType field in plugin.xml to find the correct marker type.

Cheers,
Dimitris

Re: Best way to realize constraints in meta model [message #1074315 is a reply to message #1074279]

Fri, 26 July 2013 09:42

Eclipse User

Hi Dimitris,

in this article (http://www.eclipse.org/epsilon/doc/articles/evl-gmf-integration/) and in the example code just "filesystem" was used as namespaceUri..That was a little bit confusing for me..

I used now the namespaceUri you mentioned and fixed the marker, but it still doens't work...

My project has a size of round about 40mb, so emailing will be ok for you?

Cheers,
Philipp

Re: Best way to realize constraints in meta model [message #1074627 is a reply to message #1074315]

Sat, 27 July 2013 05:11

Eclipse User

Hi Phil,

Is there any way you could slim it down (e.g. delete code that I can regenerate etc.)? If not, we could try Dropbox (dskolovos@gmail.com) if that's OK.

Cheers,
Dimitris

Re: Best way to realize constraints in meta model [message #1076065 is a reply to message #1074627]

Tue, 30 July 2013 12:37

Eclipse User

Hi Dimitris,

I've send you an email with the link to the dropbox folder..Maybe youc an have a look what's wrong there...

Another Question: Is EVL supporting Live Validation? I've read about this feature in this blog post: http://ed-merks.blogspot.de/2013/01/decorating-with-emf.html

The only thing I could figure out is a receipe (http://www.eclipse.org/epsilon/doc/articles/evl-gmf-integration/) where validation is performed whenever a diagram is saved.

Cheers,
Phil

Re: Best way to realize constraints in meta model [message #1076144 is a reply to message #1076065]

Tue, 30 July 2013 15:56

Eclipse User

Hi Phil,

Your plugin.xml looks fine but unfortunately I'm not able to run the editor as I'm missing a couple of plugins (de.itemis.xtext.utils.gmf, de.itemis.xtext.utils.jface). Could you please try with a clean GMF editor to see whether it's the interplay with Xtext that's causing this problem?

Cheers,
Dimitris

Re: Best way to realize constraints in meta model [message #1076456 is a reply to message #1076144]

Wed, 31 July 2013 08:23

Eclipse User

Hi Dimitris,

the interplay with xtext wasn't causing any problems. I had a small misstake in my check sentence, which I didn't noticed all the time. Now it's working as you can see:

index.php/fa/15787/0/

But I observed an unexpected (for me) behaviour.
It's necessary to validate from the top of the tree in order to get a correct validation message. After this it doesn't matter in which part of the tree you click on validate, it's working then like expected.
But if you didn't start validating from the top of the tree, you always get a "Validation compledted succesfully" message:

index.php/fa/15788/0/

Is this the desired behaviour?

Cheers,
Phil

Attachment: constraint_xor.JPG
(Size: 39.49KB, Downloaded 515 times)
Attachment: evl_constraint_check_error.JPG
(Size: 33.31KB, Downloaded 513 times)

Re: Best way to realize constraints in meta model [message #1076482 is a reply to message #1076456]

Wed, 31 July 2013 09:09

Eclipse User

Hi Phil,

I'm glad this works now. I'll have a look at the non-root validation issue and get back to you.

Cheers,
Dimitris

Previous Topic:	Run configurations
Next Topic:	Property view error: Exeed?

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 23:30:20 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter