Overloading Behaviour in Java

Replies

• 

  sookie

  It is because of exception hierarchy. At runtime, "null" is not passed as an object it is passed as a "null" value means no value hence it goes in exception flow and looks for nearest parent object.
  
• 

  Anoop Kumar

  Some corrections here...
  1.null is not a object type as if null would be object it should support java.lang.Object method like equals().
  
  2.Overloading returns most specific behaviour that is why when it caught an exception it returns
  RuntimeException exception object instead of Exception object.
  try this:
  
  
  

  public class testOverload {
  public void xyz(Object o) {
  System.out.println("o");
  }
  public void xyz(Integer o) {
  System.out.println("Integer");
  }
  public void xyz(String o) {
  System.out.println("String");
  }
  public void xyz(Exception o) {
  System.out.println("exc");
  }
  public void xyz(RuntimeException o) {
  System.out.println("runtime");
  }
  public static void main(String[] args) {
  testOverload t = new testOverload();
  t.xyz("dfa");
  t.xyz(123);
  t.xyz((new Object()));
  
  }
  }