| AMW + QVT [message #560014] |
Mon, 20 September 2010 14:05  |
Eclipse User |
|
|
|
Hi,
all of the examples and use case I have found include AMW and ATL, in such a way that the weaving model is an input model in an ATL transformation. Is there any example that uses QVT instead of ATL as transformation language?
Has anyone tried this combination?
Thanks and best regards,
Toñi
|
|
|
|
| Re: AMW + QVT [message #630127 is a reply to message #629621] |
Thu, 30 September 2010 13:00  |
| Eclipse User |
|
|
|
Hi Marco,
you are refering to the semi-automatic generation of weaving models,
aren't you?
That is, in a scenario in which weaving models are generated
manually, is it possible to use QVT transformations instead of ATL
transformations?
El 29/09/2010 2:27, Marcos Didonet Del Fabro escribió:
> Hi,
>
> The current implementation has been done focusing on ATL. As far as I
> know, there is no QVT equivalent.
>
> In order to do it, it would be necessary to replace the ATL metamodel
> and transformations by the QVT ones...
>
>
> Regards,
>
> Marcos.
>
>
|
|
|
|
| Re: AMW + QVT [message #631235 is a reply to message #631190] |
Wed, 06 October 2010 12:11 |
| Eclipse User |
|
|
|
Hi,
thanks for your answer. If transformations are created outside the
tool, then the functionality of amw is reduced to create weaving models.
That is, I don't have to create the weaving metamodel and I have an
editor to create weaving models, am I right?
Regards,
Toñi
El 06/10/2010 16:13, Marcos Didonet Del Fabro escribió:
> Hi
>
> I am refering to both cases, since both implementations are based on the
> same core components.
>
> This means there is no QVT-implementation available, but it is possible
> to use QVT inside the tool if you extend the existing mecanism.
> Otherwise, you as well may create the QVT transformations and execute
> them outside the tool, by taking a weaving model as input parameter,
>
> Marcos.
|
|
|
| Re: AMW + QVT [message #631281 is a reply to message #631235] |
Wed, 06 October 2010 15:34 |
| Eclipse User |
|
|
|
In the case of using QVT externally coupled with the manual creation of weaving models, you continue to use the tool for creating the weaving models, which conform to some weaving metamodel extension.
However, in the moment of execution of the transformation, you will use the produced model as input for one QVT transformation, which will be run in another plug-in
Marcos.
|
|
|
Powered by
FUDForum. Page generated in 0.05902 seconds
Home