Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MoDisco/Components/Java/Composition/Architecture"
< MoDisco | Components | Java | Composition
(→Benchmark) |
|||
| Line 4: | Line 4: | ||
[[Image:JavaApplicationMetaModel.png|frame|center|JavaApplication MetaModel]] | [[Image:JavaApplicationMetaModel.png|frame|center|JavaApplication MetaModel]] | ||
| − | == Benchmark == | + | == Benchmark == |
| − | Java Composition Model, weaving KDM Model Source and Java Model, can easily become a big model, in terms of XMI size as well as number of model elements. | + | Java Composition Model, weaving KDM Model Source and Java Model, can easily become a big model, in terms of XMI size as well as number of model elements. |
| − | First implementation resulted in a single XMI file containing all the weaving elements between both models. | + | First implementation resulted in a single XMI file containing all the weaving elements between both models. |
| − | Second implementation results in a root XMI file, referencing other xmi fragment | + | Second implementation results in a root XMI file, referencing other xmi fragment |
| + | <br> Splitting was done following this repartition : | ||
| − | + | *First resource contains the JavaApplication itself | |
| − | *First resource contains the JavaApplication itself | + | *Second resource contains all Java2Directory |
| − | *Second resource contains all Java2Directory | + | |
*One resource per package/directory | *One resource per package/directory | ||
| − | This splitting enable the browser to perform lazy loading when browsing a composite model in the MoDisco Model Browser | + | This splitting enable the browser to perform lazy loading when browsing a composite model in the MoDisco Model Browser |
| + | |||
| + | [[Image:ResourceComposition.png|frame|center|Three levels of resource]] | ||
Revision as of 03:52, 10 August 2010
DEPRECATED use Template:MoDiscoTabs and Template:MoDiscoTab as explain here : Wiki Template for MoDisco
Java Composition Metamodel
JavaApplication MetaModel
Benchmark
Java Composition Model, weaving KDM Model Source and Java Model, can easily become a big model, in terms of XMI size as well as number of model elements.
First implementation resulted in a single XMI file containing all the weaving elements between both models.
Second implementation results in a root XMI file, referencing other xmi fragment
Splitting was done following this repartition :
- First resource contains the JavaApplication itself
- Second resource contains all Java2Directory
- One resource per package/directory
This splitting enable the browser to perform lazy loading when browsing a composite model in the MoDisco Model Browser
Three levels of resource