You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When propagating methods from Java to UML, they are identified based on their name only, ignoring the parameters. This leads to multiple overloaded methods in Java being merged into a single method in UML.
A fix would require to check if a UML method already corresponds to a Java method before adding yet another correspondence from that same UML method to an overloaded version of the Java method.
The text was updated successfully, but these errors were encountered:
When propagating methods from Java to UML, they are identified based on their name only, ignoring the parameters. This leads to multiple overloaded methods in Java being merged into a single method in UML.
A fix would require to check if a UML method already corresponds to a Java method before adding yet another correspondence from that same UML method to an overloaded version of the Java method.
The text was updated successfully, but these errors were encountered: