Module 8: Interface Enhancements in Java 8

Phase

Phase 3 – Advanced Concepts

Target Audience

• Java developers familiar with interfaces
• Developers maintaining or evolving APIs
• Anyone preparing for advanced Java 8 interviews

---

1. Objective of This Module

By the end of this module, you will:

• Understand why interfaces were enhanced in Java 8
• Use default methods correctly
• Use static methods in interfaces
• Handle multiple inheritance conflicts
• Safely evolve existing interfaces

---

2. The Problem Before Java 8

Before Java 8:

• Interfaces could contain only abstract methods
• Adding a new method broke all implementing classes
• Interface evolution was risky

interface PaymentService {
    void pay();
}

Adding a new method meant updating every implementation.

---

3. Default Methods

Java 8 allows interfaces to have default method implementations.

interface PaymentService {
    void pay();

    default void logPayment() {
        System.out.println("Payment logged");
    }
}

✔ Existing implementations remain unaffected
✔ Enables backward compatibility

---

4. Why Default Methods Were Introduced

• To support API evolution
• To enhance existing interfaces (e.g., Collection, List)
• To allow behavior sharing without abstract classes

Example:

List<String> list = new ArrayList<>();
list.forEach(System.out::println);

(forEach is a default method)

---

5. Static Methods in Interfaces

Interfaces can also contain static methods.

interface Validator {
    static boolean isValid(String input) {
        return input != null && !input.isEmpty();
    }
}

Usage:

boolean valid = Validator.isValid("Java");

✔ Utility-style methods
✔ Cannot be overridden

---

6. Multiple Inheritance & Diamond Problem

Scenario

interface A {
    default void show() {
        System.out.println("A");
    }
}

interface B {
    default void show() {
        System.out.println("B");
    }
}

class C implements A, B {
}

❌ Compilation error due to ambiguity.

---

7. Resolving Default Method Conflicts

The implementing class must override the method.

class C implements A, B {
    @Override
    public void show() {
        A.super.show();
    }
}

✔ Explicit conflict resolution

---

8. Rules to Remember

• Class methods take precedence over interface default methods
• Sub-interface default methods override parent interface defaults
• Conflicts must be resolved explicitly

---

9. Real-World Use Cases

• Adding methods to public APIs
• Enhancing framework interfaces
• Providing optional behavior

Examples:

• Iterable.forEach()
• Comparator.thenComparing()

---

10. Common Mistakes

• Overusing default methods
• Treating interfaces like abstract classes
• Adding state to interfaces

---

11. Hands-On Exercises

Exercise 1

Add a default method to an existing interface.

Exercise 2

Create two interfaces with same default method and resolve conflict.

Exercise 3

Convert utility class methods to interface static methods.

---

12. Summary

• Default methods enable backward compatibility
• Static methods belong to the interface
• Interface evolution is safer in Java 8

---

13. What’s Next?

➡️ Module 9: Date & Time API (java.time)