Ambiguous references calling overloaded methods

[Marcela Blei]

public class Nulls {
  public static void main(String args[]) {
    System.out.println("dog".equals(null));
    String string = null;
    Integer i = null;
    Nulls n = new Nulls();
    //n.myMethod(null); //This gives an ambiguous reference compile error
    n.myMethod(string);
    n.myMethod(i);
  }
  public void myMethod(Integer string) {
    System.out.println("Integer");
  }
  public void myMethod(Object obj) {
    System.out.println("Object");
  }
  public void myMethod(String string) {
    System.out.println("String");
  }
}

I tried this code for the purpose of looking at the behavior of calling overloaded methods with a null value.
But I found that when I comment the myMethod method with the String argument xor with the Integer argument I don�t get a compile time error and the program runs fine with my ambiguous call.
What�s the rule on this?

[rajsim]

If you overload myMethod(Object) with myMethod(String) and call
with myMethod(null), compiler will consider myMethod(String) as
more specific and call it.
If you have myMethod(Integer) as well myMethod(String), they
are equally specific as both extend Object directly.

[This message has been edited by rajsim (edited August 07, 2000).]