[news.eclipse.technology.gmt.amw] Re: AMW plugin

[Marcos Didonet Del Fabro <marcos.didonet-del-fabro@xxxxxxxxxxxxxx>]

Hello,

Actually the weaving model is not supposed to be a metamodel in an ATL transformation.

As in the traceability example, you should use the weaving metamodel extension described 
in page one (or a similar metamodel, for example an extension created by you).

The complete metamodel is created by clicking on "save weaving metamodel in Ecore/KM3". 
This metamodel should be used as the output traceability metamodel in the ATL transformation.

The ATL transformation transforms the model elements of A into the elements of B, and 
generates a traceability model (that is a weaving model) with links between A and B.

In this traceability example, the AMW plug-in is used to visualize the weaving model.

Marcos.


Franco Bergomi wrote:
> Hello, thanks for your answer,
> actually clicking on "save weaving metamodel in ecore/km3" saves the 
> weaving metamodel conforming to Ecore or KM3.
>
> In fact I was looking at the tutorial "Generating an ATL ExecutionTrace 
> as a Traceability Weaving Model", and I wanted to obtain an analog 
> result by creating a weaving model between the 2 metamodels MA & MB .
>
> This weaving model (the one I have created) could allow to create 
> "traceability models" that could be created during the transformation 
> from A (instance of MA) to B (instance of MB), so now I'm looking how I 
> can use this weaving model  as a metamodel in an ATL transformation in 
> order to create this "traceability model" that links related A & B 
> Elements.
>
> is there a trick that allows me to use the weaving model as a MetaModel ?
> Do I have to know something particular about "references" in ecore 
> models ? (to use the references described in the weaving model)
>
> Franco.