Difference between revisions of "MoDisco/Components/FacetManager"

Revision as of 13:08, 19 November 2009

MoDisco Role

The MoDisco role component introduced the "role" concept. A role is a kind of virtual class extension. Those "virtual classes" will never have instances. An object can be conform to a role but can not be an instance of a role.

For example, assuming we have a class named Employee and two roles: "Manager" and "Developer". We will have a set of Employee instances and some of them will have the role of "Manager" or "Developer".

The goal of role concept introduction is to be able to highlight some model elements having a specific role.

The MoDisco role feature allows describing and using roles. The description is done by editing a model and the use is done through an API. The main client of this API is the MoDisco browser.

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 is conform to a role.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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 method contained in the abstract class. To create a new role attribute right-click on the role element and select the "New > New Child > RoleAttribute" button.

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

The role set is now ready to be used.

How to consult the MoDisco role set catalog trough 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 get this view select "Windows > Show view > Other ..." in the menu bar and chose "Role Set" in the list.

File:MoDisco Role newRoleSet 020.gif

The "Role set" view presents the available role sets and them roles. For each role set the description model location is point out.

How to programmatically use the MoDisco role set catalog.

Here a MoDisco role API example is provided. To have more informations 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();
		context.addRoleSet(roleSet);
		Role role = roleSet.getRole("AbstractClassDeclaration");
		if (context.isInstance(eObject, role)) {
			Object object = context.get(eObject, role
					.getEStructuralFeature("nbAbstractMethod"));
			if (object instanceof Integer) {
				Integer nbAbstractMethod = (Integer) object;
				return nbAbstractMethod;
			}
		}
		return null;
	}
}

Role Meta-model Description

The role meta-model extends the ecore meta-model and use 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 the ModelQuery class. The model queries pointed by the conditionQuery reference must return a Boolean. Those queries are used to specify how to decide if an instance is conform to a role. If the conditionQuery is empty all the instances of the class referred by role instance trough the eSuperType reference, are conform to the 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 and 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 than the query they refer.