Description Stephane Begaudeau 2014-01-09 07:37:26 EST

When you have a Java service in an odesign file, the Acceleo bridge will create an Acceleo module representing this service. For example, this class:

import a.b.c.d.MyType;

package a.b.c;

public class MyClass {
    public boolean doStuff(Lis<MyType> myType) {
        return true;
    }
}

would be "transformed" to this module:

[comment encoding=utf-8/]
[module myClass(<all the accessible meta-models>)]

[query public doStuff(myType: Sequence(MyType)): Boolean =
  invoke('a.b.c.MyClass', 'doStuff(a.b.c.d.MyType)', Sequence{myType})
/]

The problem occurs if the list of accessible meta-models contains two meta-models with the EClass MyType. Acceleo will take the first EClass accessible with the name MyType. The correct solution would be:

"[query public doStuff(myType: Sequence(myMetamodel::MyType)): Boolean ="

instead of

"[query public doStuff(myType: Sequence(MyType)): Boolean ="

This issue does not occur during the execution of the representation since the operation will be recompiled with the proper type. It only occurs during the validation of the odesign.