|
|
|
Re: Multiple Metamodel ATL transformation to Single File [message #1835346 is a reply to message #1835329] |
Tue, 01 December 2020 10:00 |
|
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.01442 seconds