| [ATL] How to handle meta-model dependencies ??? [message #669397] |
Tue, 10 May 2011 08:08 |
 Aur
Messages: 29
Registered: August 2010 |
Junior Member |
|
|
Hi all,
I am searching a way to produce an ATL transformation that uses a meta model which has some dependencies. The following figure shows the problem I am facing. (I hope so ...)
Ignoring B.ecore's dependencies, the ATL module could be something like:
module myModule;
create OUT: mmB_bis from IN: mmB;
rule B2B{
from f : mmB!B
to t : mmB_bis!B(
b1 <- f.b1
)
}
But if I want to use the dependencies, how can I produce something like:
module myModule;
create OUT: mmOut from IN: mmB;
rule B2B{
from f:mmB!B
to t: mmB_bis !B(
b1 <- f.b1
a1 <- f.a1
)
}
This rule produces error, because of the fact that mmB!B.a1 is not defined. Which is true, it is an inherited feature coming from an other ecore file.
So if someone could give me some track, that will be really helpful.
Thanks in advance,
Aurelien
|
|
|
Powered by
FUDForum. Page generated in 0.02999 seconds
] 
Search
Help
Register
Login
Home
