Bird
Raised Fist0
Javaprogramming~3 mins

Why Constructor chaining in Java? - Purpose & Use Cases

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
The Big Idea

What if you could write your constructors once and reuse them everywhere without repeating yourself?

The Scenario

Imagine you are building a class with many constructors to create objects in different ways. You write similar code in each constructor to set default values or initialize fields. This means repeating yourself a lot.

The Problem

Writing similar code in every constructor is slow and tiring. It's easy to make mistakes or forget to update all constructors when something changes. This repetition makes your code messy and hard to maintain.

The Solution

Constructor chaining lets one constructor call another in the same class. This way, you write common initialization code once and reuse it. It keeps your code clean, reduces errors, and makes updates easier.

Before vs After
Before
public class Car {
  private String color;
  private int year;

  public Car() {
    this.color = "red";
    this.year = 2020;
  }

  public Car(String color) {
    this.color = color;
    this.year = 2020;
  }

  public Car(String color, int year) {
    this.color = color;
    this.year = year;
  }
}
After
public class Car {
  private String color;
  private int year;

  public Car() {
    this("red", 2020);
  }

  public Car(String color) {
    this(color, 2020);
  }

  public Car(String color, int year) {
    this.color = color;
    this.year = year;
  }
}
What It Enables

Constructor chaining enables writing cleaner, easier-to-maintain code by reusing initialization logic across multiple constructors.

Real Life Example

Think of a smartphone app where you create user profiles. Some profiles have just a name, others have name and age, and some have name, age, and location. Constructor chaining helps set default values and avoid repeating code for each profile type.

Key Takeaways

Constructor chaining reduces repeated code in multiple constructors.

It makes your code cleaner and easier to update.

It helps avoid mistakes when initializing objects in different ways.

Practice

(1/5)
1. What is the main purpose of constructor chaining in Java?
easy
A. To allow one constructor to call another constructor in the same class
B. To inherit constructors from a parent class automatically
C. To create multiple objects with the same constructor
D. To override constructors with different names

Solution

  1. Step 1: Understand constructor chaining concept

    Constructor chaining means one constructor calls another constructor in the same class to reuse code.
  2. Step 2: Identify the correct purpose

    To allow one constructor to call another constructor in the same class correctly describes this behavior using this(...) to call another constructor.
  3. Final Answer:

    To allow one constructor to call another constructor in the same class -> Option A
  4. Quick Check:

    Constructor chaining = calling another constructor [OK]
Hint: Constructor chaining uses this(...) to call another constructor [OK]
Common Mistakes:
  • Confusing constructor chaining with inheritance
  • Thinking constructors can have different names
  • Believing constructor chaining creates multiple objects
2. Which of the following is the correct syntax to chain constructors in Java?
easy
A. this.call(); // calls another method
B. super(); // calls constructor of same class
C. this(); // must be the first statement in constructor
D. constructor(); // calls constructor by name

Solution

  1. Step 1: Recall syntax for constructor chaining

    Constructor chaining uses this(...) as the first statement inside a constructor.
  2. Step 2: Identify correct option

    this(); // must be the first statement in constructor shows this(); which is the correct syntax to call another constructor in the same class.
  3. Final Answer:

    this(); // must be the first statement in constructor -> Option C
  4. Quick Check:

    Constructor chaining syntax = this() first [OK]
Hint: Use this() as first line to chain constructors [OK]
Common Mistakes:
  • Using super() to call same class constructor
  • Calling constructor by its name directly
  • Placing this() after other statements
3. What will be the output of the following Java code?
class Test {
  Test() {
    this(5);
    System.out.print("A");
  }
  Test(int x) {
    System.out.print("B");
  }
  public static void main(String[] args) {
    new Test();
  }
}
medium
A. AB
B. BA
C. A
D. B

Solution

  1. Step 1: Trace constructor calls

    Creating new Test() calls the no-arg constructor, which calls Test(int x) first (prints "B"), then prints "A".
  2. Step 2: Determine output order

    Since Test(int x) prints "B" first, then control returns to no-arg constructor which prints "A", output is "BA".
  3. Final Answer:

    BA -> Option B
  4. Quick Check:

    Constructor chaining prints B then A [OK]
Hint: Constructor chaining prints inner constructor output first [OK]
Common Mistakes:
  • Assuming outer constructor prints before inner
  • Confusing order of constructor calls
  • Ignoring that this() must be first line
4. Identify the error in the following Java code related to constructor chaining:
class Sample {
  Sample() {
    System.out.println("Hello");
    this(10);
  }
  Sample(int x) {
    System.out.println(x);
  }
}
medium
A. Constructor chaining call this(10) must be the first statement
B. Constructor name must match class name
C. Cannot overload constructors with different parameters
D. Missing return type in constructors

Solution

  1. Step 1: Check constructor chaining rules

    In Java, the call to another constructor using this(...) must be the first statement in the constructor.
  2. Step 2: Identify the error

    Here, System.out.println("Hello") comes before this(10);, which violates the rule.
  3. Final Answer:

    Constructor chaining call this(10) must be the first statement -> Option A
  4. Quick Check:

    this() must be first line in constructor [OK]
Hint: this() call must be first statement in constructor [OK]
Common Mistakes:
  • Placing code before this() call
  • Confusing constructor overloading with chaining
  • Thinking constructors need return types
5. Given the class below, what will be the output when new Box(); is executed?
class Box {
  Box() {
    this(3, 4);
    System.out.print("X");
  }
  Box(int w, int h) {
    this(w, h, 5);
    System.out.print("Y");
  }
  Box(int w, int h, int d) {
    System.out.print("Z");
  }
}
hard
A. ZXY
B. ZY
C. XYZ
D. ZYX

Solution

  1. Step 1: Trace constructor chaining calls

    Calling new Box() calls no-arg constructor, which calls Box(int w, int h), which calls Box(int w, int h, int d).
  2. Step 2: Track printed characters in order

    The deepest constructor prints "Z" first, then returns to middle constructor which prints "Y", then returns to no-arg constructor which prints "X".
  3. Final Answer:

    ZYX -> Option D
  4. Quick Check:

    Chained constructors print Z then Y then X [OK]
Hint: Deepest constructor prints first, then unwind chain [OK]
Common Mistakes:
  • Assuming outer constructor prints first
  • Ignoring chaining order
  • Mixing up print order in nested calls