Creating custom exception class in Java - Why You Should Know This

The Big Idea

What if your program could tell you exactly what went wrong, every time?

The Scenario

Imagine you are building a program that handles different errors, like file not found or invalid user input. You try to use the built-in error messages, but they are too general and don't explain exactly what went wrong in your special case.

The Problem

Using only standard error messages can be confusing and slow down fixing problems. You might have to write many checks everywhere, and it's easy to miss important details or mix up errors. This makes your code messy and hard to understand.

The Solution

Creating a custom exception class lets you define your own error type with a clear name and message. This makes your program easier to read and debug because you know exactly what kind of problem happened. It also helps you handle errors in a clean and organized way.

Before vs After

✗ Before

if (age < 0) {
  throw new IllegalArgumentException("Invalid age");
}

✓ After

if (age < 0) {
  throw new NegativeAgeException("Age cannot be negative");
}

What It Enables

It enables you to create meaningful, specific error messages that make your program more reliable and easier to maintain.

Real Life Example

For example, in a banking app, you can create a custom exception like InsufficientFundsException to clearly show when a user tries to withdraw more money than they have.

Key Takeaways

Standard errors can be unclear and hard to manage.

Custom exceptions give clear, specific error messages.

They help keep your code clean and easier to fix.

Practice

1. What is the correct way to start creating a custom exception class in Java?

easy

A. Extend the Exception or RuntimeException class

B. Implement the Exception interface

C. Create a class with the same name as Exception

D. Use the throw keyword in the class declaration

Solution

1. Step 1: Understand Java exception hierarchy

   Custom exceptions must extend either Exception or RuntimeException to behave like exceptions.

2. Step 2: Recognize correct inheritance

   Implementing an interface or naming a class Exception does not create a proper exception class.

3. Final Answer:

   Extend the Exception or RuntimeException class -> Option A

4. Quick Check:

   Custom exception = extends Exception [OK]

Hint: Always extend Exception or RuntimeException for custom exceptions [OK]

Common Mistakes:

• Trying to implement Exception as an interface
• Naming class Exception instead of extending it
• Using throw keyword in class declaration

2. Which of the following is the correct constructor for a custom exception class named MyException?

easy

A. public MyException() { this.message = message; }

B. public void MyException(String message) { super(message); }

C. public MyException(String message) { super(message); }

D. public MyException(String message) { print(message); }

Solution

1. Step 1: Identify correct constructor syntax

   Constructors have no return type and call super(message) to pass the message to the parent Exception class.

2. Step 2: Check each option

   public MyException(String message) { super(message); } correctly defines a constructor calling super(message). public MyException() { this.message = message; } incorrectly assigns message without declaration. public void MyException(String message) { super(message); } has a void return type, so it's not a constructor. public MyException(String message) { print(message); } calls a non-existent method print.

3. Final Answer:

   public MyException(String message) { super(message); } -> Option C

4. Quick Check:

   Constructor calls super(message) = public MyException(String message) { super(message); } [OK]

Hint: Constructor must call super(message) without return type [OK]

Common Mistakes:

• Adding void return type to constructor
• Not calling super(message) in constructor
• Trying to assign message directly without declaration

3. What will be the output of this code?

class MyException extends Exception {
    public MyException(String message) {
        super(message);
    }
}

public class Test {
    public static void main(String[] args) {
        try {
            throw new MyException("Error occurred");
        } catch (MyException e) {
            System.out.println(e.getMessage());
        }
    }
}

medium

A. Error occurred

B. MyException

C. Compilation error

D. No output

Solution

1. Step 1: Understand exception throwing and catching

   The code throws a MyException with message "Error occurred" and catches it immediately.

2. Step 2: Check output from getMessage()

   The catch block prints e.getMessage(), which returns the message passed to the exception.

3. Final Answer:

   Error occurred -> Option A

4. Quick Check:

   Exception message printed = Error occurred [OK]

Hint: getMessage() prints the exception message passed in constructor [OK]

Common Mistakes:

• Expecting class name instead of message
• Thinking code won't compile due to custom exception
• Missing try-catch block causing runtime error

4. Identify the error in this custom exception class:

public class MyException extends Exception {
    public void MyException(String message) {
        super(message);
    }
}

medium

A. super(message) cannot be called in this class

B. Missing import statement for Exception

C. Class must implement Serializable interface

D. Constructor has a void return type, so it's a method, not a constructor

Solution

1. Step 1: Check constructor syntax

   Constructors must not have a return type. Here, void makes it a method, not a constructor.

2. Step 2: Understand consequences

   Without a proper constructor, the class uses default constructor which does not call super(message), causing errors when throwing with message.

3. Final Answer:

   Constructor has a void return type, so it's a method, not a constructor -> Option D

4. Quick Check:

   Constructor no return type = Constructor has a void return type, so it's a method, not a constructor [OK]

Hint: Constructors never have a return type, not even void [OK]

Common Mistakes:

• Adding void return type to constructor
• Assuming import Exception is needed
• Thinking super() cannot be called in subclass

5. You want to create a custom unchecked exception named InvalidDataException. Which is the correct way to define it?

hard

A. public class InvalidDataException implements RuntimeException {
public InvalidDataException(String message) {
super(message);
}
}

B. public class InvalidDataException extends RuntimeException {
public InvalidDataException(String message) {
super(message);
}
}

C. public class InvalidDataException extends Exception {
public InvalidDataException(String message) {
super(message);
}
}

D. public class InvalidDataException extends Throwable {
public InvalidDataException(String message) {
super(message);
}
}

Solution

1. Step 1: Understand checked vs unchecked exceptions

   Unchecked exceptions extend RuntimeException, checked exceptions extend Exception.

2. Step 2: Analyze each option

   public class InvalidDataException extends RuntimeException { public InvalidDataException(String message) { super(message); } } correctly extends RuntimeException with proper constructor. public class InvalidDataException extends Exception { public InvalidDataException(String message) { super(message); } } creates a checked exception. public class InvalidDataException implements RuntimeException { public InvalidDataException(String message) { super(message); } } tries to implement an exception class, which is invalid. public class InvalidDataException extends Throwable { public InvalidDataException(String message) { super(message); } } extends Throwable directly, which is not recommended for custom exceptions.

3. Final Answer:

   public class InvalidDataException extends RuntimeException { public InvalidDataException(String message) { super(message); } } -> Option B

4. Quick Check:

   Unchecked exception = extends RuntimeException [OK]

Hint: Unchecked exceptions extend RuntimeException, not Exception [OK]

Common Mistakes:

• Extending Exception for unchecked exceptions
• Trying to implement exception classes
• Extending Throwable directly