This annotation allows to identify the method through a constant, thus avoiding issues when
running obfuscation tools.
For example, the following code:
public class MyClass {
public static final String METHOD_NAME = "get";
@Alias(METHOD_NAME)
public int getOne() {
return 1;
}
}
allows to asynchronously call the method independently from its original name like:
JRoutine.on(instance(new MyClass())).aliasMethod(MyClass.METHOD_NAME).asyncCall();
The same considerations apply to static class methods.
This annotation is used to decorate methods that are to be invoked in an asynchronous way.
Note that the piece of code inside such methods will be automatically protected so to avoid
concurrency issues. Though, other parts of the code inside the same class will be not.
In order to prevent unexpected behaviors, it is advisable to avoid using the same class fields
(unless immutable) in protected and non-protected code, or to call synchronous methods through
routines as well.
Finally, be aware that a method might need to be made accessible in order to be called. That
means that, in case a
SecurityManager is installed, a security exception might
be raised based on the specific policy implemented.
Remember also that, in order for the annotation to properly work at run time, you will need to
add the following rules to your Proguard file (if employing it for shrinking or obfuscation):
-keepattributes RuntimeVisibleAnnotations
-keepclassmembers class ** {
@com.github.dm.jrt.annotation.Alias *;
}
Created by davide-maestroni on 01/22/2015.