Comments on: @Override annotation

By: Thomas

Thomas — Thu, 07 May 2009 22:02:30 +0000

Class A is not overriding the void method1(); method signature but you are implementing it. Effectively you are overriding the implementation. Even this would not be a override

abstract class K {
public abstract void method1();
}

class A extends K {
public void method1() {
}
}

Because you are implementing an abstract method

If you were to override it you would have

abstract class K {
public void method1() {
}
}

class A extends K {
@Override
public void method1() {
}
}

By: Penguin

Penguin — Sun, 22 Mar 2009 23:46:47 +0000

Maybe you are right, Java 5 thinks the interface is different from class, so implementation of the interface method is not consider overriding super class.

By: szehau

szehau — Fri, 20 Mar 2009 06:10:31 +0000

I’m not sure why there is difference between Java5 and Java6. From what I think is when a class implements a interface, all methods in the interface must be defined in the class else you will get compile time error. So it doesn’t matter whether you put “@Override” or not for the interface’s methods.

You say the Javadoc says “Indicates that a method declaration is intended to override a method declaration in a superclass”. Maybe Java5 think a interface is an interface and is difference from class. While Java6 maybe simply ignore the checking as it is not necessary to “@Override” an interface method as it is a must for a class to define it.

By: discount shower curtains

discount shower curtains — Sun, 15 Mar 2009 06:29:31 +0000

hey thanks for commenting on my blog, every little bit helps. take care.