Should we @Override an interface’s method implementation?

by

You should use @Override whenever possible. It prevents simple mistakes from being made. Example:

class C {
    @Override
    public boolean equals(SomeClass obj){
        // code ...
    }
}

This doesn’t compile because it doesn’t properly override public boolean equals(Object obj).

The same will go for methods that implement an interface (1.6 and above only) or override a Super class’s method.

More Related Contents:

  1. Abstract class in Java
  2. Why is there no multiple inheritance in Java, but implementing multiple interfaces is allowed?
  3. Is there more to an interface than having the correct methods
  4. What is an interface in Java?
  5. Why to use Interfaces, Multiple Inheritance vs Interfaces, Benefits of Interfaces?
  6. Why java classes do not inherit annotations from implemented interfaces?
  7. How should I have explained the difference between an Interface and an Abstract class?
  8. Why does Eclipse complain about @Override on interface methods?
  9. Can we create an object of an interface?
  10. Inner class within Interface
  11. How one interface can be used for different background android tasks?
  12. Do/can abstract classes replace interfaces? [duplicate]
  13. When do I have to use interfaces instead of abstract classes? [duplicate]
  14. Should you always Code To Interfaces In Java [closed]
  15. interface as a method parameter in Java
  16. How to create custom annotation with code behind
  17. Why are interfaces preferred to abstract classes?
  18. How much interfaces a class file can implement [closed]
  19. The purpose of interfaces continued
  20. Polymorphism vs Overriding vs Overloading
  21. How to supply value to an annotation from a Constant java
  22. @Resource vs @Autowired
  23. The difference between the Runnable and Callable interfaces in Java
  24. Is polymorphism possible without inheritance?
  25. How to use Hibernate @Any-related annotations?
  26. Why java.lang.Object is not abstract? [duplicate]
  27. Spring annotation-based DI vs xml configuration?
  28. Should methods that throw RuntimeException indicate it in method signature?
  29. Setting a JPA timestamp column to be generated by the database?
  30. Methods With Same Name as Constructor – Why?

Leave a Comment