Community
Participate
Working Groups
From AQL we can call Java service. And with 2 Java methods with same signature having only parameter type difference, i.e. one method parameter is a subType of the second method parameter, we have the second method called when passing a instance of the subType. With service: interpreter there is no polymorphism feature, then only the first Java method will be called. This bugzilla is a feature request to have a homonogeous behavior on Java service call between AQL and service: interpreters.
Maybe we could reuse the same logic as the one used by AQL itself in AbstractService.isLowerOrEqualParameterTypes(). It seems slef-contained enough that we could copy and adapt it (its from AQL, part of Acceleo, so no IP/licensing issue).
Created attachment 260279 [details] Sample project to reproduce Scenario to reproduce: 1. Import the attached project 2. Open the diagram and see "EClass label : c1" for the EClass and "ENamedElement label : p1" for the EPackage, here we have polymorphism because the label expression use "aql:self.getLabel()" 3. Now update the odesign to have "service:getLabel()" as label expression for both mappings and save 4. Switch to the diagram editor and see the result of refresh : "ENamedElement label : c1" for the EClass and "ENamedElement label : p1" for the EPackage, here we see that we don't have polymorphism with service: interpreter.
