In the Plugin V2 interface I notice that method overloading give unpredictable result, so if 2 method have the same method name the one called remotely is not predictable.
I think is a limitation on how the RPC interface are implemented and I cannot find a reference of it in the documentation.
Should be mentioned that all the method should have unique name in the documentation?
hi, can you share more context here, please?
an RPC interface can not have two identical methods, since it’s a limitation of JVM. If the interface has unique method signatures, our compiler plugin must produce proper harness and resolve to a proper backend method implementation indeed.
What I noticed is this, if the same Interface has 2 method with the same method but different signature, usually only one will be called. If I’ve time I try to build a small example for it.
Create a demo project forking the template for modular project:
I just added 3 button in the chat that called an overload method in the remote api.
I verify that only one of the two is called (the one with no param).
@Nikita.Katkov anything else needed on this limitation?