Skip to main content
Jump to: navigation, search

Difference between revisions of "MoDisco/Components/Java/Composition/Documentation/0.9"

(Description)
(Description)
Line 13: Line 13:
 
[[Image:JavaApplicationMetaModel.png|frame|center|JavaApplication Metamodel]]
 
[[Image:JavaApplicationMetaModel.png|frame|center|JavaApplication Metamodel]]
  
Note : the references ''java2DirectoryChildren'' and ''java2FileChildren'' are expected to be containment references. For some technical reasons (memory usage tuning via lazy loading), they are not containment to make sure that the ''Java2Directory'', ''Java2File'' and ''JavaNodeSourceRegion'' instances are managed in their own graph compared with ''JavaApplication'' instances (See benchmark).
+
Note : the references ''java2DirectoryChildren'' and ''java2FileChildren'' are expected to be containment references. For some technical reasons (memory usage tuning via lazy loading), they are not containment to make sure that the ''Java2Directory'', ''Java2File'' and ''JavaNodeSourceRegion'' instances are managed in their own graph compared with ''JavaApplication'' instances (See [http://wiki.eclipse.org/MoDisco/Components/Java/Composition/Architecture#Benchmark benchmark]).
  
 
==Java Composition Discoverer==
 
==Java Composition Discoverer==

Revision as of 12:58, 19 August 2010

DEPRECATED use Template:MoDiscoTabs and Template:MoDiscoTab as explain here : Wiki Template for MoDisco

Java Composition Metamodel

Description

This metamodel JavaApplication aims at weaving a MoDisco Java Model with a MoDisco KDM Inventory Model. It relies on the core metamodel described in the kdm.source extension framework.

Such a metamodel allows to link java nodes to their physical position in the source files (JavaNodeSourceRegion metaclass owning startLine endLine properties).

As proposed in kdm.source extension framework, the reference JavaASTNodeSourceRegion.javaNode derived from ASTNodeSourceRegion.node. So as the Java2File.javaUnit from CodeUnit2File.unit.

JavaApplication Metamodel

Note : the references java2DirectoryChildren and java2FileChildren are expected to be containment references. For some technical reasons (memory usage tuning via lazy loading), they are not containment to make sure that the Java2Directory, Java2File and JavaNodeSourceRegion instances are managed in their own graph compared with JavaApplication instances (See benchmark).

Java Composition Discoverer

Description

MoDisco provides a discoverer associated to the metamodel definition described here. The discovery takes as an entry one workspace Java project. The first step of the discovery creates one Java and one Kdm inventory model, using the associated discoverers. The second step creates the links, in a third resource, as JavaApplication metamodel instances, between the two models.

Java and kdm inventory discovery

Requirements

To use the plug-ins 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:

https://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco/plugins/trunk/org.eclipse.modisco.java.composition/

https://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco/plugins/trunk/org.eclipse.modisco.java.composition.discoverer/

Back to the top