Eclipse Community Forums: ATL » Multiple Metamodel ATL transformation to Single File

Help

Home

Home » Modeling » ATL » Multiple Metamodel ATL transformation to Single File

Show: Today's Messages :: Show Polls :: Message Navigator

Multiple Metamodel ATL transformation to Single File [message #1835314]

Mon, 30 November 2020 15:32

Burak Karaduman

Messages: 84
Registered: July 2018

Member

Dear All,

Is it possible to write whole transformation outputs to the single xmi file, when the ATL transformation is triggered?. As an Example, result of the transformation A->B and C->D transformation result will be embedded into same file.

Thanks.

Report message to a moderator

Re: Multiple Metamodel ATL transformation to Single File [message #1835328 is a reply to message #1835314]

Mon, 30 November 2020 18:46

Dennis Wagelaar

Messages: 581
Registered: September 2012
Location: Belgium

Senior Member

Yes, this is possible in principle. How depends on your specific transformations' input and output metamodels.

Cheers,
Dennis

Report message to a moderator

Re: Multiple Metamodel ATL transformation to Single File [message #1835329 is a reply to message #1835328]

Mon, 30 November 2020 18:50

Burak Karaduman

Messages: 84
Registered: July 2018

Member

Dear Dennis,

Thanks for your answer, could you please provide more specific example? Even if I have done some research about it, still I couldn't figure it out. The metamodels will be different and in seperated ecore files. So, my aim is to transform the models of these different metamodels into one single XMI file. As a result, can ATL perform such an action?

Report message to a moderator

Re: Multiple Metamodel ATL transformation to Single File [message #1835346 is a reply to message #1835329]

Tue, 01 December 2020 10:00

Dennis Wagelaar

Messages: 581
Registered: September 2012
Location: Belgium

Senior Member

In EMF this is possible: you can refer to individual EClasses by simple hyperlink from each EMF model, regardless of in which .ecore file those EClasses are located.

In ATL, each model conforms to exactly one metamodel, which is enforced at the file level: each model file conforms to one metamodel file. In order to have a model conform to multiple metamodel files (or nsURI's), which is common in EMF, you need to define a "spanning metamodel" in ATL. A spanning metamodel is simply a new ecore file with e.g. a single abstract EClass in it, that inherits from one EClass from each ecore file you want to "import". The ATL metamodel loader recognises the dependencies on other .ecore files, and will load them automatically.

Cheers,
Dennis

Report message to a moderator