Skip to main content
Jump to: navigation, search


Mailing ListForums
Help Wanted
Bug Day
Browse SourceProject Set File

How to create a model role set

The first step is to create a MoDisco project.

The second step is to create a query set. This query set will store boolean queries indicating if an object conforms to a role.

Right-click on the MoDisco project and select the "New > Other ..." button.

MoDisco Role newRoleSet 001.gif

Select "Role Model" and press the "Next" button

MoDisco Role newRoleSet 002.gif

Choose a name for your model role set (My.roleSet in the example) and press "Next".

MoDisco Role newRoleSet 003.gif

Select "RoleSet" in the "Model Object" list and press "Finish"

MoDisco Role newRoleSet 004.gif

MoDisco Role newRoleSet 005.gif

Open the "My.roleSet" file and open the "Properties View"

MoDisco Role newRoleSet 006.gif

Set the name of the role set and make sure that the role set name is the same as the containing file name ("My" in the example). The nsURI and prefix must also be filled.

MoDisco Role newRoleSet 007.gif

Load the resources containing the meta-model extended by the role set. To load a meta-model resource the user must use the "Load meta-model resource" action.

MoDisco Role newRoleSet 008.gif

In this example, we choose to use the Java meta-model.

MoDisco Role newRoleSet 009.gif

Fill the "Extended package" field with the ePackages containing the virtually extended meta-model.

MoDisco Role newRoleSet 010.gif

Right click on the RoleSet element and choose the "New Child > Role" action to create a role.

MoDisco Role newRoleSet 011.gif

Set the role name and the class that the role will extend.

MoDisco Role newRoleSet 012.gif

To specify how to know if an object conforms to a role, we have to provide a boolean query. To provide this query we have to load the model containing its description.

MoDisco Role newRoleSet 013.gif

The query has to be referred to using the MoDisco protocol: "modisco:/query/<querySetName>". In the example, we use the "My" query set.

MoDisco Role newRoleSet 014.gif

Once the query set resource is referenced, we just have to select the query describing the role. In the example this query is named "isAbstract".

MoDisco Role newRoleSet 015.gif

At this step, if we save the model, the "red cross" should disappear from the file icon. This means that the role set model is now valid.

MoDisco Role newRoleSet 016.gif

If the role has specific attributes or references which can be calculated, we can declare them. In this example, we will declare an attribute indicating the number of abstract methods contained in the abstract class. To create a new role attribute right-click on the role element and select the "New Child > RoleAttribute" item.

MoDisco Role newRoleSet 017.gif

The attribute's type and name must be set. The "Value Query" field must be filled with a reference to a query which is used to calculate the attribute's value. This query must have the same type as the attribute and be applicable to the virtually extended class.

MoDisco Role newRoleSet 018.gif

The role set is now ready to be used.

How to consult the MoDisco role set catalog through the UI

If a role set model is valid, it is registered in the role set catalog. To consult the role set catalog, we can use the "Role Set" view.

To open this view select "Windows > Show view > Other ..." in the menu bar and choose "Role Set" in the list.

MoDisco Role newRoleSet 019.gif File:MoDisco Role newRoleSet 020.gif

The "Role set" view presents the available role sets and their roles. For each role set the location of its description model is pointed out.

MoDisco Role newRoleSet 021.gif

How to programmatically use the MoDisco role set catalog

Here is an example of using the MoDisco role API. For more information please refer to the JavaDoc.

import org.eclipse.emf.ecore.EObject;
import org.eclipse.gmt.modisco.infra.query.core.exception.ModelQueryException;
import org.eclipse.gmt.modisco.infra.role.Role;
import org.eclipse.gmt.modisco.infra.role.RoleSet;
import org.eclipse.gmt.modisco.infra.role.core.RoleContext;
import org.eclipse.gmt.modisco.infra.role.core.RoleSetCatalog;
import org.eclipse.gmt.modisco.infra.role.core.exception.ModiscoRoleException;

public class Example {

	public Integer getNbAbstractMethod(EObject eObject)
			throws ModelQueryException, ModiscoRoleException {
		RoleSet roleSet = RoleSetCatalog.getSingleton().getRoleSet("My");
		RoleContext context = new RoleContext();
		Role role = roleSet.getRole("AbstractClassDeclaration");
		if (context.isInstance(eObject, role)) {
			Object object = context.get(eObject, role
			if (object instanceof Integer) {
				Integer nbAbstractMethod = (Integer) object;
				return nbAbstractMethod;
		return null;

Role Meta-model Description

MoDisco Role metamodel.png

The role meta-model extends the ecore meta-model and uses the query meta-model.

A RoleSet is a kind of EPackage. A RoleSet contains roles through the eClassifier reference. A role is a kind of EClass.

For a role instance, the eSuperType reference must be set to specify which class the role virtually extends.

The role class has one specific reference: conditionQuery. The conditionQuery reference points to the ModelQuery class. The model queries pointed to by the conditionQuery reference must return a Boolean. Those queries are used to specify how to decide whether an instance conforms to a role. If the conditionQuery is empty then all the instances of the class referred to by the role instance through the eSuperType reference conform to this role.

A role contains roleAttributes and roleReferences through the eStructuralFeature reference. The RoleAttribute and RoleReference classes have a common super class: RoleStructuralFeature. The RoleStructuralFeature has one reference named valueQuery pointing to the ModelQuery class. The valueQuery is used to compute the role structural feature value. The roleAttribute and roleReference must have the same type as the query they refer to.

Back to the top