Skip to main content
Jump to: navigation, search


< MoDisco‎ | Components‎ | KDMSourceExtension
Revision as of 06:47, 5 November 2010 by (Talk | contribs) (Added Code Source Synchronization Framework Title)

Mailing ListForums
Help Wanted
Bug Day
Browse SourceProject Set File

KDM.Source extension : a core metamodel for weaving Code models and KDM Inventory models

The component proposes a small framework for building weaving information between code models (Java, C++, ...) and physical resources (disk files and directories).

This framework reuses the KDM "Source" subpackage, which proposes a model for physical resources, known as "Inventory Model" (see figure here)

KDM inventory model also proposes SourceRegion/SourceRef concepts for weaving other kdm models (kdm code models, ...) with physical representation. Some references exist from other KDM subpackages to the SourceRef concept.

KDM Source Metamodel subpart (from the KDM Specification v 1.1)

MoDisco proposes to compose KDM inventory models with non-KDM models. For generic reuse reasons, a new metamodel extending KDM Source has been created.

A subpart of KDM Source model is extended for linking the SourceRegion concept with non-KDM elements, via the ASTNodeSourceRegion metaclass.

Moreover a recurrent pattern, in such a model composition, is to link KDM SourceFile with a code model element. Such a link is represented with CodeUnit2File metaclass.

MoDisco KDM Source extension Metamodel

This is a core metamodel that the developer should extend for describing a composition between a specific code metamodel and kdm.source.

How to create a composition metamodel between Code models and KDM Inventory models

Given a particular code metamodel (Such as the Java one), MoDisco proposes to extend KDMSourceExtension to define a metamodel composition between inventory models and code models.

The ASTNodeSourceRegion should be subclassed, and a reference to one concrete code metaclass should "specialize" the ASTNodeSourceRegion->node:EObject reference (one simple way is to set the new reference as derivated from the generic one).

(TODO : an opposite reference should be described for allowing navigation from code elements to the SourceRegion instances --> waiting for facet shortcut evolution to come)

In most cases the CodeUnit2File will be subclassed.

A reference example of such a composition metamodel is the Java Application example.

Java and kdm composition metamodel (extract)

How to develop a discoverer for the composition between code and KDM inventory models


After describing a composition metamodel, the contributor/adopter has to write an associated discoverer. Such a discoverer will instantiate elements for the composition metamodel described before (JavaSourceRegions...) Such a discoverer will have to manipulate the both kdm.source and code models.

A discoverer for the related code model is a prerequisite. The [Java Discoverer] is an example. Such a discoverer is not supposed to instantiate SourceRegions subclasses. To avoid ambiguity, we will talk about it as a "leaf code discoverer".

The composite discoverer should, in most cases, invoke the leaf discoverers (kdm.source and code). Another way is to provide the leaf models as parameters values to the composite discoverer.

A kdm.source model can be discovered using the [KDM Source discoverer]. Note that such a discoverer only provides a representation of files/directories. It does not instantiate SourceRegions subclasses.

A reference example of such a composition dicoverer is the Java Application discoverer example (Java class DiscoverKDMSourceAndJavaModel).

Composition discovery overview

Using the abstract AbstractComposedKDMSourceDiscoverer discoverer Java class

An abstract java class is proposed to facilitate and factorize some common code : AbstractComposedKDMSourceDiscoverer
This abstract discoverer proposes a process with four steps :

  1. initialize the composite model (to implement)
  2. discover the kdm.source model (already implemented)
  3. discover the others leaf models (to implement). In most cases there is only one code model
  4. terminate the discovery (weaving or saving actions)

Using the AbstractComposedKDMSourceDiscoverer is not mandatory.

Instrumenting the leaf code discoverers for retrieving visited source regions

In most cases, code discoverers have access to physical localization for each portion of code that is modeled.

There are two ways for a composite discoverer to catch such an information when invoking the leaf discoverer :

  • subclass some leaf discoverer implementation classes.
  • add a listener to the leaf discoverer to listen for source regions visit events.

The second way implies that the leaf discoverer extends the org.eclipse.modisco.kdm.source.extension.discovery.AbstractRegionDiscoverer class to support the registering of org.eclipse.modisco.kdm.source.extension.discovery.SourceRegionVisitListener.

AbstractRegionDiscoverer.notifyRegionSourceVisit must be called when appropriate from inside the leaf discoverer.

The [Java discoverer] implementation class illustrates such a pattern application.

The following figure illustrates the architecture for leaf and composite discoverers related to a CSharp metamodel.

Applicative Architecture for CSharp leaf and composite discoverers example

Instantiate source region nodes

Once the composite discoverer has the capability to retrieve information about sources regions visited and associated code model elements, it will instantiate the SourceRegion.

Resources Distribution and memory usage

Creating one SourceRegion instance for each code model element may induce some memory usage issues. Considering a given code metamodel, it may be interesting to have a strategy for dispatching model elements (from the composition model) into more than one XMI resource file.

Thus, EMF lazy resource loading mechanism enables opening and working with some subpart of the model.

A reference implementation for this strategy is in the [Java Application discovery].

Code Source Synchronization Framework


To use the plug-in you need:

  • JDK 1.5 or above
  • a version of Eclipse 3.6 or above with the following set of plug-ins installed
  • EMF 2.5.0 or higher

Source Repository

All of the source code is stored in a public source repository, which you can access at:

Back to the top