What if you could upgrade your code without rewriting everything?
Why Default methods in Java? - Purpose & Use Cases
Start learning this pattern below
Jump into concepts and practice - no test required
Imagine you have many classes implementing the same interface, and you want to add a new method to that interface. Without default methods, you must update every class to add this new method, even if the implementation is the same.
This manual update is slow and error-prone. You might forget to add the new method in some classes, causing your program to break. It's like having to rewrite the same instructions in every manual instead of updating a single template.
Default methods let you add new methods with a standard implementation directly in the interface. Classes can use this default or override it if needed. This saves time and avoids mistakes by centralizing the common code.
interface MyInterface {
void existingMethod();
}
class A implements MyInterface {
public void existingMethod() { /*...*/ }
// must add newMethod() here manually
}interface MyInterface {
void existingMethod();
default void newMethod() {
System.out.println("Default behavior");
}
}
class A implements MyInterface {
public void existingMethod() { /*...*/ }
// no need to add newMethod() unless custom behavior needed
}It enables evolving interfaces without breaking existing code, making your programs easier to maintain and extend.
Think of a smartphone app interface where you add a new feature. Default methods let all existing apps keep working without forcing every developer to rewrite their code immediately.
Default methods let interfaces provide standard method code.
They prevent breaking changes when interfaces evolve.
They reduce repetitive code and errors in many classes.
Practice
default methods in Java interfaces?Solution
Step 1: Understand interface method rules before Java 8
Interfaces could only declare abstract methods without bodies, forcing all implementing classes to define them.Step 2: Role of default methods
Default methods allow interfaces to provide method bodies, so new methods can be added without breaking existing classes.Final Answer:
To allow interfaces to have method bodies without breaking existing implementations -> Option DQuick Check:
Default methods add bodies to interfaces safely [OK]
- Confusing default methods with abstract methods
- Thinking default methods enable multiple inheritance of classes
- Believing default methods are private helper methods
Solution
Step 1: Recall default method syntax
Default methods start with the keyworddefault, followed by the return type, method name, and body.Step 2: Check each option
default void show() { System.out.println("Hello"); } matches the correct syntax:default void show() { ... }. Others have incorrect order or keywords.Final Answer:
default void show() { System.out.println("Hello"); } -> Option AQuick Check:
default + return type + method name + body = correct syntax [OK]
- Placing default keyword after return type
- Using default as a method modifier incorrectly
- Omitting method body for default methods
interface A {
default void greet() {
System.out.println("Hello from A");
}
}
class B implements A {
public void greet() {
System.out.println("Hello from B");
}
}
public class Test {
public static void main(String[] args) {
A obj = new B();
obj.greet();
}
}Solution
Step 1: Understand method overriding with default methods
Class B overrides the defaultgreet()method from interface A with its own implementation.Step 2: Determine which greet() is called
At runtime, the overridden method in class B is called, printing "Hello from B".Final Answer:
Hello from B -> Option AQuick Check:
Overridden method in class wins [OK]
- Assuming default method runs instead of overridden
- Expecting compilation error due to default method
- Confusing runtime and compile-time behavior
interface X {
default void display() {
System.out.println("X display");
}
}
interface Y {
default void display() {
System.out.println("Y display");
}
}
class Z implements X, Y {
public void display() {
// ???
}
}What should be done inside class Z's
display() method to fix the error?Solution
Step 1: Understand diamond problem with default methods
Class Z implements two interfaces X and Y, both having default display() methods, causing ambiguity.Step 2: Resolve ambiguity by overriding and calling specific interface method
Class Z must override display() and explicitly call one interface's default method usingX.super.display()orY.super.display().Final Answer:
Call X.super.display() or Y.super.display() to resolve ambiguity -> Option BQuick Check:
Explicit super call fixes default method conflict [OK]
- Ignoring ambiguity and expecting code to compile
- Trying to remove interfaces instead of overriding
- Making method abstract in a concrete class
interface Printer {
default void print() {
System.out.println("Printing document");
}
}
interface Scanner {
default void print() {
System.out.println("Scanning document");
}
}
class MultiFunctionDevice implements Printer, Scanner {
public void print() {
// Combine both behaviors here
}
}Which code inside
print() correctly combines both default methods?Solution
Step 1: Understand calling multiple default methods
To combine behaviors, the class must explicitly call each interface's default method usingInterfaceName.super.method().Step 2: Check each option
Printer.super.print(); Scanner.super.print(); correctly calls both default methods. print(); print(); causes infinite recursion. super.print(); is invalid syntax. Printer.print(); Scanner.print(); is invalid because interfaces cannot be called like classes.Final Answer:
Printer.super.print(); Scanner.super.print(); -> Option CQuick Check:
Use InterfaceName.super.method() to call multiple defaults [OK]
- Calling method recursively causing stack overflow
- Using super.print() without interface name
- Trying to call interface methods like static methods
