Reflection Basico en Android

el
Learn Java for Android Development: Reflection Basics

Learn Java for Android Development: Reflection Basics

Shane Conder & Lauren Darcey
Tutorial Details
  • Program: Java with Android Focus
  • Difficulty: Beginner
  • Estimated Completion Time: 45-60 Minutes
This entry is part 5 of 13 in the series Learn Java for Android Development
In this tutorial, you’ll become familiar with the concept of Java reflection: the ability of a class or object to examine details about its own implementation programmatically.


Android applications are written in the Java, a programming language that supports reflection—the ability of an object to examine itself. In this tutorial, you’ll learn the basics of Java reflection, including how to inspect the methods and fields of a given class, check for the availability of specific methods, and other practical tasks you may need to use when developing for different versions of the Android SDK.

What You’ll Need

Technically, you don’t need any tools to complete this tutorial but you will certainly need them to develop Android applications.

To develop Android applications (or any Java applications, for that matter), you need a development environment to write and build applications. Eclipse is a very popular development environment (IDE) for Java and the preferred IDE for Android development. It’s freely available for Windows, Mac, and Linux operating systems.

For complete instructions on how to install Eclipse (including which versions are supported) and the Android SDK, see the Android developer website.

Why Use Reflection?

Reflection gives developers the flexibility to inspect and determine API characteristics at runtime, instead of compile time. Within the security constraints imposed by Java (e.g. use of public, protected, private), you can then construct objects, access fields, and invoke methods dynamically. The Java Reflection APIs are available as part of the java.lang.reflect package, which is included within the Android SDK for developers to use.

So what does this have to do with Android development? Well, with each new version of the Android SDK, classes, interfaces, methods, etc. are added, updated, and (less frequently) removed. However, Android developers often want to target devices running different versions of Android with a simple application package. To do this, Android developers may use reflection techniques to determine, at runtime, if a specific class or method is available before trying to use it. This allows the developer to leverage new APIs where available while still supporting the older devices—all in the same application.

Inspecting Classes

Java classes are represented at runtime using the Class (java.lang.Class) class. This class provides the starting point for all reflection APIs. Within this class, you’ll find many methods for inspecting different aspects of a class, such as its fields, constructors, methods, permissions, and more. You can also use the Class method called forName() to load a non-primitive class (e.g. not int, but Integer) by name dynamically at runtime, instead of at compile time:
view plaincopy to clipboardprint?
  1. String sClassName = "android.app.NotificationManager";  
  2. try {  
  3.     Class classToInvestigate = Class.forName(sClassName);   
  4.   
  5.     // Dynamically do stuff with this class  
  6.     // List constructors, fields, methods, etc.  
  7.   
  8. } catch (ClassNotFoundException e) {  
  9.     // Class not found!  
  10. } catch (Exception e) {  
  11.     // Unknown exception  
  12. }  
The class (in this case, NotificationManager) need not have the corresponding import statement in your code; you are not compiling in this class into your application. Instead, the class loader will load the class dynamically at runtime, if possible. You can then inspect this Class object and use the reflection techniques described in the rest of this tutorial.

Inspecting the Constructors Available Within a Class

You can inspect the constructors available within a given Class. To get just the constructors that are publicly available, use getConstructors(). However, if you want to inspect those methods specifically declared within the class, whether they are public or not, use getDeclaredConstructors() instead. Both methods return an array of Constructor (java.lang.reflect.Constructor) objects.

For example, the following code iterates through the declared constructors of a class:
view plaincopy to clipboardprint?
  1. Constructor[] aClassConstructors = classToInvestigate.getDeclaredConstructors();  
  2. for(Constructor c : aClassConstructors){  
  3.     // Found a constructor c  
  4. }  
Once you have a valid Constructor object, you can inspect its parameters and even declare a new instance of the class using that constructor with the newInstance() method.

Inspecting the Fields Available Within a Class

You can inspect the fields (or attributes) available within a given Class. To get just the methods that are publicly available, including inherited fields, use getFields(). However, if you want to inspect those fields specifically declared within the class (and not inherited ones), whether they are public or not, use getDeclaredFields() instead. Both methods return an array of Field (java.lang.reflect.Field) objects.
For example, the following code iterates through the declared fields of a class:
view plaincopy to clipboardprint?
  1. Field[] aClassFields = classToInvestigate.getDeclaredFields();  
  2. for(Field f : aClassFields){  
  3.     // Found a field f  
  4. }  
You can also check for a specific public field by name using the getField() method. For example, to check for the EXTRA_CHANGED_PACKAGE_LIST field of the Intent class (which was added in API Level 8, or Android 2.2), you could use:
view plaincopy to clipboardprint?
  1. String sClassName = "android.content.Intent";  
  2. try {  
  3.     Class classToInvestigate = Class.forName(sClassName);  
  4.     String strNewFieldName = "EXTRA_CHANGED_PACKAGE_LIST";  
  5.     Field newIn22 = classToInvestigate.getField(strNewFieldName);  
  6.   
  7. } catch (ClassNotFoundException e) {  
  8.     // Class not found  
  9. } catch (NoSuchFieldException e) {  
  10.     // Field does not exist, likely we are on Android 2.1 or older  
  11.     // provide alternative functionality to support older devices  
  12. } catch (SecurityException e) {  
  13.     // Access denied!  
  14. } catch (Exception e) {  
  15.     // Unknown exception  
  16. }  
Once you have a valid Field object, you can get its name using the toGenericString() method. If you have the appropriate permissions, you can also access the value of that class field using the appropriate get() and set() methods.

Inspecting the Methods Available Within a Class

You can inspect the methods available within a given Class. To get just the methods that are publicly available, including inherited methods, use getMethods(). However, if you want to inspect those methods specifically declared within the class (without inherited ones), whether they are public or not, use getDeclaredMethods() instead. Both methods return an array of Method (java.lang.reflect.Method) objects.

For example, the following code iterates through the declared methods of a class:
view plaincopy to clipboardprint?
  1. Method[] aClassMethods = classToInvestigate.getDeclaredMethods();  
  2. for(Method m : aClassMethods)  
  3. {  
  4.     // Found a method m  
  5. }  
Once you have a valid Method object, you can get its name using the toGenericString() method. You can also examine the parameters used by the method and the exceptions it can throw. Finally, if you have the appropriate permissions, you can also call the method using the invoke() method.

Inspecting Inner Classes

You can inspect the inner classes defined within a Class using getDeclaredClasses() method. This method will return an array of Class (java.lang.class) objects declared within the parent class. These classes can then be inspected like any other.

Inspecting Member Modifiers

You can also inspect the flags and security settings—called modifiers—associated with a given Class, Field, or Method using the getModifiers() method. Interesting modifiers include whether the component is public, private, protected, abstract, final, or static (amongst others).
For example, the following code checks the security modifiers of a class:
view plaincopy to clipboardprint?
  1. int permissions = classToInvestigate.getModifiers();  
  2.   
  3. if(Modifier.isPublic(permissions)) {  
  4.     // Class is Public  
  5. }  
  6. if(Modifier.isProtected(permissions)) {  
  7.     // Class is Protected  
  8. }  
  9. if(Modifier.isPrivate(permissions)) {  
  10.     // Class is Private  
  11. }  
Keep in mind that you cannot dynamically access or invoke any class, method, or field using reflection that you would not normally be able to access at compile-time. In other words, regular class security is still applied at runtime.

Inspecting Class Metadata

You can also inspect the metadata—called annotations—associated with a given class, field or method using the getAnnotations() method. Interesting metadata associated with a class might include information about deprecation, warnings, and overrides, among other things.
For example, the following code checks the metadata available for the AbsoluteLayout class. Since this class was deprecated in Android 1.5, one of the annotations returned is @java.lang.Deprecated() when this code is run on Android 2.2:
view plaincopy to clipboardprint?
  1. String sClassName = "android.widget.AbsoluteLayout";  
  2. try {  
  3.     Class classToInvestigate = Class.forName(sClassName);  
  4.   
  5.     Annotation[] aAnnotations = classToInvestigate.getDeclaredAnnotations();  
  6.     for(Annotation a : aAnnotations)  
  7.     {  
  8.         // Found an annotation, use a.toString() to print it out  
  9.     }  
  10.   
  11. } catch (ClassNotFoundException e) {  
  12.     // Class not found!  
  13. } catch (Exception e) {  
  14.     // Handle unknown exception!  
  15. }  
Similarly, you could simply check for the existence of a specific annotation, such as deprecation, by its type:
view plaincopy to clipboardprint?
  1. if(classToInvestigate.isAnnotationPresent(java.lang.Deprecated.class) == true)  
  2. {  
  3.     // Class is deprecated!  
  4. }  

Reflection: Handy for Debugging

You can also use reflection to assist with debugging. For example, you might want to use the class keyword to access the underlying class data for a given type:
view plaincopy to clipboardprint?
  1. import android.app.Activity;  
  2. …  
  3. String strClassName = Activity.class.getName();    // android.app.Activity  
You can also get class information from a variable instance using the getClass() method of the Object class (which is therefore inherited by all classes in Java):
view plaincopy to clipboardprint?
  1. String silly = "Silly String!";  
  2. Class someKindOfClass = silly.getClass();  
  3. String strSillyClassName = someKindOfClass.getName();    // java.lang.String  
If you want to check the class of a variable, using instanceof is more appropriate. See the previous tutorial on instanceof for more details.
Similarly, you might want to use the getClass() method with the this keyword to check the name of the class you’re currently in and include this information as part of your debug logging to LogCat:
view plaincopy to clipboardprint?
  1. String strCurrentClass = this.getClass().getName();    // e.g. the current Activity  
  2. Log.v(strCurrentClass, "Debug tag is current class.");  

Why Not To Use Reflection

As you’ve seen, reflection can be used to great effect, especially when you are unsure if a specific class or method is available at compile time. Reflection does, however, have some drawbacks, including reduced performance and the loss of the strong typing and safe coding practices enforced at compile time. It’s best to use reflection sparingly, but do use it when needed.

Wrapping Up

Reflection is a powerful tool that Java developers can use to explore packages and APIs programmatically at runtime. While reflection operations come at a cost, they give the developer the flexibility that is sometimes essential for getting the job done. Android developers frequently use these simple reflection techniques to test for the availability of specific classes, interfaces, methods, and fields at runtime, enabling them to support different versions.

About the Authors

Mobile developers Lauren Darcey and Shane Conder have coauthored several books on Android development: an in-depth programming book entitled Android Wireless Application Development and Sams TeachYourself Android Application Development in 24 Hours. When not writing, they spend their time developing mobile software at their company and providing consulting services. They can be reached at via email to androidwirelessdev+mt@gmail.com, via their blog at androidbook.blogspot.com, and on Twitter @androidwireless.