Skip to main content
Jump to: navigation, search

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

(Java Composition Discoverer)
(Java Composition Discoverer)
Line 1: Line 1:
 
{{MoDiscoJavaCompositionTabs}}
 
{{MoDiscoJavaCompositionTabs}}
 +
 +
== Java Composition Metamodel ==
 +
This metamodel aims at weaving a MoDisco Java Model with a MoDisco KDM Source one.
 +
 +
The Java Composition Discoverer uses this metamodel to create liaison between model elements.
 +
 +
In addition to that, some weaving is done to link java nodes to their physical position in the analysed code. Those elements are stored in the JavaNodeSourceRegion.
 +
 +
References java2DirectoryChildren and java2FileChildren should be containment references, but then browsers load all the resources instead of performing lazy loading (see section Benchmark below). This is due to the use of getAllContent() method which retrieve external references.
 +
 +
[[Image:JavaApplicationMetaModel.png|frame|center|JavaApplication MetaModel]]
  
 
==Java Composition Discoverer==
 
==Java Composition Discoverer==

Revision as of 09:27, 18 August 2010

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

Java Composition Metamodel

This metamodel aims at weaving a MoDisco Java Model with a MoDisco KDM Source one.

The Java Composition Discoverer uses this metamodel to create liaison between model elements.

In addition to that, some weaving is done to link java nodes to their physical position in the analysed code. Those elements are stored in the JavaNodeSourceRegion.

References java2DirectoryChildren and java2FileChildren should be containment references, but then browsers load all the resources instead of performing lazy loading (see section Benchmark below). This is due to the use of getAllContent() method which retrieve external references.

JavaApplication MetaModel

Java Composition Discoverer

Back to the top