Why would both a parent and child class implement the same interface?

by

As I understand interfaces (and my experimentation has reinforced), there is no purpose to having both the parent and the child implement the same interface.

No. Technically, it is completely redundant.

It does however document the fact that you intend SoapFacadeImpl to be a SoapFacade and it ensures that you get a compile error, if you (or someone else) decides to remove implements SoapFacade from the base class.

You see this pattern everywhere in the standard Java Collections API. ArrayList implements List even though its base class (AbstractList) already, does. Same holds for HashSet / AbstractSet and the Set interface.

More Related Contents:

  1. Why is there no multiple inheritance in Java, but implementing multiple interfaces is allowed?
  2. Implements vs extends: When to use? What’s the difference?
  3. What is an interface in Java?
  4. Explicitly calling a default method 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. Do interfaces inherit from Object class in java
  8. How should I have explained the difference between an Interface and an Abstract class?
  9. Why are class static methods inherited but not interface static methods?
  10. When do I have to use interfaces instead of abstract classes? [duplicate]
  11. How can interfaces replace the need for multiple inheritance when have existing classes
  12. I am not able to send values to the baseclass constructor
  13. Extends JFrame vs. creating it inside the program
  14. How can I get a list of all the implementations of an interface programmatically in Java?
  15. Overriding vs Hiding Java – Confused
  16. Emulate annotation inheritance for interfaces and methods with AspectJ
  17. Java abstract interface
  18. How one interface can be used for different background android tasks?
  19. If a Marker Interface does not have any methods, how does it work?
  20. Class is not abstract and does not override abstract method
  21. JPA: Implementing Model Hierarchy – @MappedSuperclass vs. @Inheritance
  22. Java: Casting from List to List when B implements A?
  23. Why we should not use protected static in java
  24. Overriding a super class’s instance variables
  25. Why are variables declared with their interface name in Java? [duplicate]
  26. Java: Interface with new keyword how is that possible?
  27. Anonymous vs named inner classes? – best practices?
  28. Why are interfaces preferred to abstract classes?
  29. Java overloading and inheritance rules
  30. How to serialize a class with an interface?

Leave a Comment