|
| Re: [ATL] matched rule: imperative part without target section [message #499249 is a reply to message #495145 ] |
Fri, 20 November 2009 09:57  |
Vincent MAHE Messages: 26 Registered: July 2009 |
Junior Member |
|
|
mats a écrit :
> hello everyone,
> I'm actually an ATL virgin, but I've found an interesting problem:
> I've got a transformation with two input models which shall be merged
> into one new model based on some rules. It can happen, that an element
> x1 of input1 and an element x2 of input2 are marged to a new element
> xNew in the output. But based on the informations in x1 and x2 (if they
> eliminate each other) no element shall be created in the output. I first
I may suggest you match on input1 element and catch the corresponding
input2 element in "using" section with allInstances() + select
|
|
|