Skip to main content

How does covariant overriding method work?

Java 5.0 permits covariant overriding: an overriding method may have a result type that is a subtype of the method it overrides.
 
class A {
  int x = 5;
}
class B extends A {
  int x = 6;
}

class CovariantObj {  
  public A getObject() {
    System.out.println("In A");
    return new A();
  }
}

class SubCovariantObj extends CovariantObj {
  public B getObject() {
    System.out.println("In B");
    return new B();
  }
  public static void main(String[] args) {
    CovariantObj c = new SubCovariantObj();
    System.out.println(c.getObject().x);
  }
}
The output is
In B
5
Why the output of above code is 5 after printing "In B"? The c.getObjec() returns an instance of B class.
To make overriding works properly for covariant overriding case, Java compiler inserts a synthetic bridge method that is A getObject() method into the SubCovariantObj class. The bridge method only is encoded directly in JVM byte code. For example, the JVM byte code is similar to the following code:

class SubCovariantObj extends CovariantObj {
  public B getObject() {
    System.out.println("In B");
    return new B();
  }
  public A getObject() {
    return this.getObject();
  }
  ...
}

Apparently what's happening is that when the runtime type of the object is SubCovariantObj, a call to getObject() still invokes the overridden method by polymorphism, but if the reference type is CovariantObj, then the call is made through the bridge method, and so the return type in that case is A. We know that accessing a field (data member) of an object is determined by the type of reference not the current instance class holded by the reference. That is why it prints out 5.

Click below links to know more

Comments

Popular posts from this blog

Java Health Center - Overview and Features

This video highlights the features available in Health Center. Health Center is a low-processor and memory usage diagnostic tool for monitoring the status of a running IBM Java Virtual Machine (JVM). Health Center provides live information and recommendations in each of the following areas: - Classes: information about classes being loaded - Environment: details of the configuration and system of the monitored application - Garbage Collection: information about the Java heap and pause times - Locking: information about contention on inflated locks - Profiling: sampling profile of Java methods including call paths

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag...

Java Garbage Collection

Explain Garbage collection mechanism in Java? Garbage collection is one of the most important features of Java. The purpose of garbage collection is to identify and discard objects that are no longer needed by a program so that their resources can be reclaimed and reused. A Java object is subject to garbage collection when it becomes unreachable to the program in which it is used. Garbage collection is also called automatic memory management as JVM automatically removes the unused variables/objects (value is null) from the memory. Every class inherits finalize() method from java.lang.Object, the finalize() method is called by garbage collector when it determines no more references to the object exists. In Java, it is good idea to explicitly assign null into a variable when no more in use. In Java on calling System.gc() and Runtime.gc(), JVM tries to recycle the unused objects, but there is no guarantee when all the objects will garbage collected. Garbage collection is an automatic pro...