Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operations in different interfaces but with the same name #2095

Closed
PaulWu7323 opened this issue Jun 11, 2018 · 1 comment · Fixed by #2101

Comments

@PaulWu7323
Copy link

commented Jun 11, 2018

As discussed in the Yakindu User group: https://groups.google.com/forum/embed/?place=forum/yakindu-user#!topic/yakindu-user/epCpV0LRqMg

Steps to reproduce the issue:

  1. Two operations with the same name but in two different interfaces. For example:
interface PlusOne:
operation add(num:integer):integer
interface PlusTwo:
operation add(num:integer):integer
  1. Create two Java classes with the interface names and implement the methods. For example:
PlusOne.java
public class PlusOne {
    public long add(long num){
        return num+1;
    }
}

PlusTwo.java
public class PlusTwo {
    public long add(long num){
        return num+2;
    }
}
  1. In the run configuration, add the Java class names to the Operation Class field.

  2. Only one of the methods is invoked in the simulation.

    As shown in the above image, only the add method implemented in PlusOne.java is invoked so both num1 and num2 are 2.

Expected Behavior: The operations should be invoked according to the interface names. That is, Yakindu should match between interface names and Java class names.

Thanks.

@andreasmuelder

This comment has been minimized.

Copy link
Member

commented Jun 11, 2018

Thanks for reporting!

@andreasmuelder andreasmuelder added this to the Inbox milestone Jun 11, 2018
@andreasmuelder andreasmuelder self-assigned this Jun 19, 2018
@andreasmuelder andreasmuelder modified the milestones: Inbox, S44 Jun 19, 2018
andreasmuelder added a commit that referenced this issue Jun 19, 2018
andreasmuelder added a commit that referenced this issue Jun 19, 2018
* Check first for class names with same name as interface #2095

* removed sysout
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.