Welcome!

Java Authors: Elizabeth White, Pat Romanski, Liz McMillan, Carmen Gonzalez, Robert Reeves

Related Topics: Java

Java: Article

Reflection & Introspection: Objects Exposed

Reflection & Introspection: Objects Exposed

One of the salient aspects of the Java language is the control it gives to developers for dynamically generating and reusing code. This allows the language to offer Java programmers the ability to write code in which the actual behavior is determined at runtime. Of the eleven buzzwords used to define Java, this article is going to focus on the dynamic nature of the Java programming language.

One of the salient aspects of the Java language is the control it gives to developers for dynamically generating and reusing code. This allows the language to offer Java programmers the ability to write code in which the actual behavior is determined at runtime. Of the eleven buzzwords used to define Java, this article is going to focus on the dynamic nature of the Java programming language.Introspection Uses Reflection
Reflection and introspection are very closely related. Reflection is a low-level facility that allows the code to examine the internals of any class or object at runtime. Introspection builds on this facility and provides a more convenient interface for examining Beans. In fact, the relationship between reflection and introspection is very similar to the relationship between JavaBeans and other Java classes. JavaBeans are simply normal Java objects with certain design patterns enforced in their nomenclature. Introspection assumes these design patterns on the object that it is inspecting and uses low-level reflection to examine the object's internals.

The Reflection API
The Reflection API became a part of core Java with release 1.1 of the JDK. The API is defined across the following:

  • The new methods added to the java.lang.Class class in JDK 1.1
  • The java.lang.reflect package defined in JDK1.1

    The class java.lang.Class contains methods that return instances of classes/interfaces defined in the java.lang.reflect package. A detailed description of the API is beyond the scope of this article and can be found in any standard Java text. However, the classes that comprise the Reflection API are listed in Table 1.

    The Introspection API
    The Introspection API consists of several classes in the java.beans package. Again, a detailed description of the API is beyond the scope of this article and can be found in any standard Java text. The main classes in the Introspection API are listed in Table 2.

    The Costs of Usage
    Reflection and Introspection are powerful tools that contribute to the flexibility provided by the Java language. However, these APIs should be used only as needed and after taking into account the costs associated with their usage:

  • Reflection and Introspection method calls have a substantial performance overhead.
  • Using reflection makes the code much more complex and harder to understand than using direct method calls.
  • Errors in method invocation are discovered at runtime instead of being caught by the compiler.
  • The code becomes type-unsafe.

    The Reflection and Introspection APIs should be used only when other forms of object-oriented programming are not appropriate.

    The following examples demonstrate the use of Reflection and Introspection to develop some useful Java utilities.

    Cookie Factory
    Our first example illustrates the use of Reflection to build a utility that allows us to instantiate objects of types derived from a "Cookie" interface. The actual type of the object instantiated is determined by a String parameter, which contains the name of the actual class. The code for the example is shown in Listings 1and 2.

    Listing 1 defines the Cookie interface and the derived classes. The Cookie interface is simply a marker interface which is implemented by the classes FortuneCookie and MisFortuneCookie. Both these classes define a single static method which prints out a string and returns a new instance of the respective class.

    Listing 2 shows the CookieFactory class which is capable of producing objects derived from the "Cookie" interface. It defines a single method createCookie that takes a String parameter, className. The Class corresponding to this name is obtained from the Class class by calling

    c = Class.forName(className);

    Once we have the class, we need to obtain the method to be called on it. The name of the method is "newCookie." In this example, we are assuming that the name of the method is available at this point. The parameter types for the method are filled in an array of type Class and this is used to get the actual Method object as follows:

    method = c.getMethod("newCookie", pTypes);

    Once the Method object is available, the static method is invoked on the class after constructing an array of Objects that contains the actual parameter instances:

    cookie = (Cookie)(method.invoke(c, params));

    A simple tester for the class is provided in the main() method. This first constructs the CookieFactory and then creates instances of the FortuneCookie and MisFortuneCookie class. The output from the program is shown in Figure 3.

    An X-Ray Class
    Our second example illustrates the use of reflection to build a utility that allows us to view all the methods, constructors, fields, interfaces and inheritance for a supplied class. The class being X-rayed is specified by a String parameter which contains the name of the actual class. The code for the example is shown in Listing 4.

    In order for the X-ray class program to determine the methods, constructors, fields and interfaces contained in the requested class, it must instantiate an object of the class by calling:

    c = Class.forName(className);

    After instantiating the class, the utility determines the selected operation on that class based on a second user-supplied string parameter, which can have one of the following values:

    localMethods
    allMethods
    Constructors
    fields
    interface
    inheritance

    The local methods contained in the specified class may be found by calling:

    methodList = c.getDeclaredMethods();

    This call returns a Method[] that contains all the methods declared in the local class including private, protected and public. This call excludes inherited methods. A list of all the public methods, both inherited and local, may be obtained by calling:

    methodList = c.getMethods();

    Constructor methods are not included in the return Method[] of this call. Retrieving a list of constructors for a specific class can be accomplished by calling:

    constructorList = c.getDeclaredConstructors();

    This call returns a constructor[] that contains all of the private, protected and public constructors declared on the local class. A list that includes only the public constructors can be constructed by calling:

    constructorList = c.getConstructors();

    Class variables can be retrieved as Field[] information. To access a complete list of fields from a class including private, protected and public, we call:

    fieldList = c.getDeclaredFields();A list that includes only the public fields can be retrieved by calling:

    fieldList = c.getFields();

    Information concerning the interfaces implemented by a class can be accessed by calling:

    interfaceList = c.getInterfaces();

    This call returns a Class[] that contains all of the interfaces implemented by the local class. Notice that this call doesn't have a getDeclaredInterfaces() counterpart like the other methods.

    To access the inheritance information in the class, we get the name of each one of the superclasses in the inheritance tree. This is done in a while loop by calling:

    classRef = c.getSuperclass();

    We use this mechanism to return a class[] with all of the classes that participate in the extension of the local class. The output of the program for obtaining the inheritance hierarchy of the java.applet.Applet class is given in Figure 4.

    Notice that of the various methods presented on this section, the only method that recursively provided information contained in its inheritance tree was the c.getMethods() call. The other methods only provided information contained by the local class.

    An X-Ray Bean
    Our third example illustrates the use of Introspection to build a utility that allows us to view all the methods, properties and events for a supplied JavaBean class. The Bean being X-rayed is specified by a String parameter which contains the name of the actual Bean class. The code for the example is shown in Listing 3.

    In order for the X-ray Bean program to determine the methods, properties and events contained in the requested class, it must instantiate an object of the class by calling:

    c = Class.forName(className);

    After instantiating the class, the utility must access the BeanInfo for the instantiated Bean. BeanInfo data can be accessed via the Introspector class by calling:

    bi = Introspector.getBeanInfo(c);

    Next, the utility determines the selected operation on that class based on the second user-supplied parameter entered at the command line (i.e., methods, properties and events). The localMethods contained by the specified Bean can be found by calling:

    methodDescriptorList = bi.getMethodDescriptors();

    This call returns a MethodDescriptor[] that contains a description of all of the methods contained by this Bean. The type of method descriptor returned by this call contains a complete list of all the public methods contained within the inheritance tree of this Bean. In order to access the actual method instances, we need to iterate through the methodDescriptionList and obtain the method by calling:

    methodRef = methodDescriptorList[i].getMethod();

    From each one of these values, we are able to build a Method[] list that can be displayed by the utility. This includes no constructor method information. To access the Bean constructor information, you must use reflection.

    Bean properties can be retrieved via PropertyDescriptors by calling:

    PropertyDescriptorList = bi.getPropertyDescriptors();

    This call returns a PropertyDescriptor[] that contains a description of all of the properties contained by this Bean. This includes name, readMethod, writeMethod, type, EditorClass, etc. Our utility uses this information to get the readMethod, writeMethod and property name via the PropertyDescriptor superclass (i.e., FeatureDescriptor) by calling:

    methodRef = PropertyDescriptorList[i].getReadMethod();
    methodRef = PropertyDescriptorList[i].getWriteMethod();
    propertyName = PropertyDescriptorList[i].getName();

    Bean events can be retrieved via EventSetDescriptors by calling:

    eventSetDescriptorList = bi.getEventSetDescriptors();

    This call returns an EventSetDescriptor[] that contains a description of all the methods associated with each event for this Bean. Our utility uses this information to get a Method[] for each one of the returned events in the eventSetDescriptorList. This is accomplished by calling:

    methodList = eventSetDescriptorList[i].getListenerMethods();

    This information is used to identify the methods associated to each one of the listener methods.

    Information concerning the interfaces implemented by a class can be accessed by calling:

    interfaceList = c.getInterfaces();

    This call returns a class[] that contains all the interfaces implemented by the local class. Notice that this call doesn't have a getDeclaredInterfaces() counterpart like the other methods.

    The output from the program for examining the events in the class, com.sun.swing.Jpanel is shown in Figure 5.

    Conclusion
    In this article, we took a look at the Reflection and Introspection APIs and used them to develop several useful utilities for Java development. In our next article, we will use the concepts and utilities introduced here to develop a new category of dynamically generated adapters called Dynamic Adapters.

    The traditional Adapter design pattern is defined as follows: Adapter: "Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces." [Design Patterns: Elements of Resuable Object-Oriented Software, Gamma et. al., Addison Wesley, 1995.]

    Adapters are used when the input and output interfaces are known at compile-time. Dynamic Adapters will allow a program to dynamically map the interfaces at runtime. We will examine these patterns in more detail in the next article.

  • More Stories By Ajit Sagar

    Ajit Sagar is Associate VP, Digital Transformation Practice at Infosys Limited. A seasoned IT executive with 20+ years experience across various facts of the industry including consulting, business development, architecture and design he is architecture consulting and delivery lead for Infosys's Digital Transformation practice. He was also the Founding Editor of XML Journal and Chief Editor of Java Developer's Journal.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    @ThingsExpo Stories
    The industrial software market has treated data with the mentality of “collect everything now, worry about how to use it later.” We now find ourselves buried in data, with the pervasive connectivity of the (Industrial) Internet of Things only piling on more numbers. There’s too much data and not enough information. In his session at @ThingsExpo, Bob Gates, Global Marketing Director, GE’s Intelligent Platforms business, to discuss how realizing the power of IoT, software developers are now focused on understanding how industrial data can create intelligence for industrial operations. Imagine ...
    The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, discussed single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example t...
    Today’s enterprise is being driven by disruptive competitive and human capital requirements to provide enterprise application access through not only desktops, but also mobile devices. To retrofit existing programs across all these devices using traditional programming methods is very costly and time consuming – often prohibitively so. In his session at @ThingsExpo, Jesse Shiah, CEO, President, and Co-Founder of AgilePoint Inc., discussed how you can create applications that run on all mobile devices as well as laptops and desktops using a visual drag-and-drop application – and eForms-buildi...
    There is no doubt that Big Data is here and getting bigger every day. Building a Big Data infrastructure today is no easy task. There are an enormous number of choices for database engines and technologies. To make things even more challenging, requirements are getting more sophisticated, and the standard paradigm of supporting historical analytics queries is often just one facet of what is needed. As Big Data growth continues, organizations are demanding real-time access to data, allowing immediate and actionable interpretation of events as they happen. Another aspect concerns how to deliver ...
    The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
    Scott Jenson leads a project called The Physical Web within the Chrome team at Google. Project members are working to take the scalability and openness of the web and use it to talk to the exponentially exploding range of smart devices. Nearly every company today working on the IoT comes up with the same basic solution: use my server and you'll be fine. But if we really believe there will be trillions of these devices, that just can't scale. We need a system that is open a scalable and by using the URL as a basic building block, we open this up and get the same resilience that the web enjoys.
    In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect at GE, and Ibrahim Gokcen, who leads GE's advanced IoT analytics, focused on the Internet of Things / Industrial Internet and how to make it operational for business end-users. Learn about the challenges posed by machine and sensor data and how to marry it with enterprise data. They also discussed the tips and tricks to provide the Industrial Internet as an end-user consumable service using Big Data Analytics and Industrial Cloud.
    Things are being built upon cloud foundations to transform organizations. This CEO Power Panel at 15th Cloud Expo, moderated by Roger Strukhoff, Cloud Expo and @ThingsExpo conference chair, addressed the big issues involving these technologies and, more important, the results they will achieve. Rodney Rogers, chairman and CEO of Virtustream; Brendan O'Brien, co-founder of Aria Systems, Bart Copeland, president and CEO of ActiveState Software; Jim Cowie, chief scientist at Dyn; Dave Wagstaff, VP and chief architect at BSQUARE Corporation; Seth Proctor, CTO of NuoDB, Inc.; and Andris Gailitis, C...
    How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happens, where data lives and where the interface lies. For instance, it's a mix of architectural styles ...
    The Industrial Internet revolution is now underway, enabled by connected machines and billions of devices that communicate and collaborate. The massive amounts of Big Data requiring real-time analysis is flooding legacy IT systems and giving way to cloud environments that can handle the unpredictable workloads. Yet many barriers remain until we can fully realize the opportunities and benefits from the convergence of machines and devices with Big Data and the cloud, including interoperability, data security and privacy.
    Technology is enabling a new approach to collecting and using data. This approach, commonly referred to as the "Internet of Things" (IoT), enables businesses to use real-time data from all sorts of things including machines, devices and sensors to make better decisions, improve customer service, and lower the risk in the creation of new revenue opportunities. In his General Session at Internet of @ThingsExpo, Dave Wagstaff, Vice President and Chief Architect at BSQUARE Corporation, discuss the real benefits to focus on, how to understand the requirements of a successful solution, the flow of ...
    Cloud Expo 2014 TV commercials will feature @ThingsExpo, which was launched in June, 2014 at New York City's Javits Center as the largest 'Internet of Things' event in the world.
    "People are a lot more knowledgeable about APIs now. There are two types of people who work with APIs - IT people who want to use APIs for something internal and the product managers who want to do something outside APIs for people to connect to them," explained Roberto Medrano, Executive Vice President at SOA Software, in this SYS-CON.tv interview at Cloud Expo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
    Performance is the intersection of power, agility, control, and choice. If you value performance, and more specifically consistent performance, you need to look beyond simple virtualized compute. Many factors need to be considered to create a truly performant environment. In his General Session at 15th Cloud Expo, Harold Hannon, Sr. Software Architect at SoftLayer, discussed how to take advantage of a multitude of compute options and platform features to make cloud the cornerstone of your online presence.
    In this Women in Technology Power Panel at 15th Cloud Expo, moderated by Anne Plese, Senior Consultant, Cloud Product Marketing at Verizon Enterprise, Esmeralda Swartz, CMO at MetraTech; Evelyn de Souza, Data Privacy and Compliance Strategy Leader at Cisco Systems; Seema Jethani, Director of Product Management at Basho Technologies; Victoria Livschitz, CEO of Qubell Inc.; Anne Hungate, Senior Director of Software Quality at DIRECTV, discussed what path they took to find their spot within the technology industry and how do they see opportunities for other women in their area of expertise.
    Wearable devices have come of age. The primary applications of wearables so far have been "the Quantified Self" or the tracking of one's fitness and health status. We propose the evolution of wearables into social and emotional communication devices. Our BE(tm) sensor uses light to visualize the skin conductance response. Our sensors are very inexpensive and can be massively distributed to audiences or groups of any size, in order to gauge reactions to performances, video, or any kind of presentation. In her session at @ThingsExpo, Jocelyn Scheirer, CEO & Founder of Bionolux, will discuss ho...
    DevOps Summit 2015 New York, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that it is now accepting Keynote Proposals. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long development cycles that produce software that is obsolete at launch. DevOps may be disruptive, but it is essential.
    Almost everyone sees the potential of Internet of Things but how can businesses truly unlock that potential. The key will be in the ability to discover business insight in the midst of an ocean of Big Data generated from billions of embedded devices via Systems of Discover. Businesses will also need to ensure that they can sustain that insight by leveraging the cloud for global reach, scale and elasticity.
    We’re no longer looking to the future for the IoT wave. It’s no longer a distant dream but a reality that has arrived. It’s now time to make sure the industry is in alignment to meet the IoT growing pains – cooperate and collaborate as well as innovate. In his session at @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, will examine the key ingredients to IoT success and identify solutions to challenges the industry is facing. The deep industry expertise behind this presentation will provide attendees with a leading edge view of rapidly emerging IoT oppor...
    “With easy-to-use SDKs for Atmel’s platforms, IoT developers can now reap the benefits of realtime communication, and bypass the security pitfalls and configuration complexities that put IoT deployments at risk,” said Todd Greene, founder & CEO of PubNub. PubNub will team with Atmel at CES 2015 to launch full SDK support for Atmel’s MCU, MPU, and Wireless SoC platforms. Atmel developers now have access to PubNub’s secure Publish/Subscribe messaging with guaranteed ¼ second latencies across PubNub’s 14 global points-of-presence. PubNub delivers secure communication through firewalls, proxy ser...