[EMFTVM] Problem with inout model in ANT lauch file [message #1333836] |
Mon, 05 May 2014 08:51 |
Victor Pavon Messages: 50 Registered: April 2012 Location: Spain |
Member |
|
|
Hello,
I have defined an ATL transformation with an inout model. In the Eclipse launch configuration I have defined that the input model is located in a folder, but the update input model is serialized in other folder, this configuration work properly. The problems occours when I try to defined this launch configuration in an ANT Task. I defined the loadMetamodel and loadModel tasks, also I have defined de inoutput property for the emftvm.run task but I don't know where set the output path for the inoutmodel.
<emftvm.run modulepath="platform:/resource/migraria.m2m.strutsConfig_java_MIGRARIAMVCViewAndModel2MIGRARIAMVC_Controller/transformations/" module="strutsCfgJavaMVCViewModel2MVCController">
<metamodel name="mmMIGRARIAMVC"/>
<inoutmodel name="inMIGRARIAMVC" as="IN"/>
<outputmodel name="trace" as="trace" wspath="migraria.m2m.strutsConfig_java_MIGRARIAMVCViewAndModel2MIGRARIAMVC_Controller/mTarget/trace.xmi"/>
</emftvm.run>
Víctor Pavón,
Research at Quercus Software Engineering Group
University of Extremadura, Spain.
|
|
|
|
|
|
|
|
Re: [EMFTVM] Problem with inout model in ANT lauch file [message #1340756 is a reply to message #1339588] |
Thu, 08 May 2014 06:55 |
Victor Pavon Messages: 50 Registered: April 2012 Location: Spain |
Member |
|
|
I attach the build.xm and this is the model transformation head
module strutsCfgJavaMVCViewModel2MVCController;
create OUT: mmMIGRARIAMVC refining IN: mmMIGRARIAMVC, inJava: mmJava, inStrutsConfig: mmStrutsConfig, inModelTrace : mmTrace;
This is an excerpt of the output model generated when I run the transformation using Eclipse launch:
<operations xsi:type="Controller:DataOperationCall" name="confDAO.get" dataOperation="//@model/@objects.1/@operations.3">
<params xsi:type="Controller:DataOperationCallParameter" name="confId" instance="//@controller/@controlFlows.0/@instances.1" parameter="//@model/@objects.1/@operations.3/@parameters.0"[/color]/>
<return name="DeclarationFragment conf" return="//@model/@objects.1/@operations.3/@return" instance="//@controller/@controlFlows.0/@instances.2"/>
</operations>
And this is the excerpt of the model generated running the transformation with ANT task
<operations xsi:type="Controller:DataOperationCall" name="confDAO.get">
<params xsi:type="Controller:DataOperationCallParameter" name="confId" instance="//@controller/@controlFlows.0/@instances.1">
<parameter xsi:type="Model:DataOperationParameter" href="../mSource/migraria_view_and_model.xmi#//@model/@objects.1/@operations.3/@parameters.0"/>
</params>
<return name="DeclarationFragment conf" instance="//@controller/@controlFlows.0/@instances.2">
<return xsi:type="Model:DataOperationReturn" href="../mSource/migraria_view_and_model.xmi#//@model/@objects.1/@operations.3/@return"/>
</return>
<dataOperation href="../mSource/migraria_view_and_model.xmi#//@model/@objects.1/@operations.3"/>
</operations>
The differences are in the attributes dataOperation of element operation, parameter of element param and return of element return.
-
Attachment: build.xml
(Size: 2.21KB, Downloaded 175 times)
Víctor Pavón,
Research at Quercus Software Engineering Group
University of Extremadura, Spain.
[Updated on: Thu, 08 May 2014 06:59] Report message to a moderator
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05001 seconds