Why Throwing custom exceptions in Java? - Purpose & Use Cases

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 checks user input for errors. Without custom exceptions, you only get generic error messages like "Something went wrong." This makes it hard to know exactly what the problem is.

The Problem

Using only built-in exceptions means you get vague messages that don't explain the specific issue. This slows down fixing bugs and confuses users because the errors are not clear or helpful.

The Solution

Throwing custom exceptions lets you create clear, meaningful error messages tailored to your program's needs. This helps you catch and handle specific problems easily and makes your code cleaner and more understandable.

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 precise error handling that improves debugging and user feedback by clearly identifying what went wrong.

Real Life Example

For example, in a banking app, you can throw a custom exception like InsufficientFundsException to clearly show when a withdrawal fails due to lack of money.

Key Takeaways

Generic errors are unclear and hard to fix.

Custom exceptions give clear, specific error messages.

This makes your program easier to debug and maintain.

Practice

1. What is the main purpose of throwing a custom exception in Java?

easy

A. To speed up the program execution.

B. To automatically fix errors in the program.

C. To create a specific error type with a clear message for better error handling.

D. To avoid writing any error handling code.

Solution

1. Step 1: Understand what custom exceptions do

   Custom exceptions let programmers define specific error types that describe particular problems clearly.

2. Step 2: Identify the purpose of throwing them

   Throwing a custom exception signals a specific error condition, making it easier to catch and handle that error properly.

3. Final Answer:

   To create a specific error type with a clear message for better error handling. -> Option C

4. Quick Check:

   Custom exceptions improve error clarity = A [OK]

Hint: Custom exceptions clarify errors for better handling [OK]

Common Mistakes:

• Thinking exceptions fix errors automatically
• Believing exceptions speed up code
• Assuming exceptions remove need for error handling

2. Which of the following is the correct syntax to throw a custom exception named MyException?

easy

A. throw new MyException();

B. throw MyException();

C. throw exception MyException();

D. throw exception new MyException();

Solution

1. Step 1: Recall Java syntax for throwing exceptions

   In Java, to throw an exception, you use the keyword throw followed by new and the exception class constructor.

2. Step 2: Match the syntax with the options

   Only throw new MyException(); uses the correct syntax: throw new MyException();

3. Final Answer:

   throw new MyException(); -> Option A

4. Quick Check:

   Throw syntax = throw new Exception() [OK]

Hint: Always use 'throw new ExceptionName()' to throw exceptions [OK]

Common Mistakes:

• Omitting the 'new' keyword
• Adding extra keywords like 'exception'
• Using parentheses without 'new'

3. What will be the output of the following Java code?

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

public class Test {
    public static void check(int num) throws MyException {
        if (num < 0) {
            throw new MyException("Negative number not allowed");
        } else {
            System.out.println("Number is " + num);
        }
    }

    public static void main(String[] args) {
        try {
            check(-5);
        } catch (MyException e) {
            System.out.println(e.getMessage());
        }
    }
}

medium

A. Negative number not allowed

B. Compilation error

C. Number is -5

D. No output

Solution

1. Step 1: Analyze the check method behavior

   If the input number is less than 0, it throws a MyException with message "Negative number not allowed"; otherwise, it prints the number.

2. Step 2: Follow the main method execution

   Main calls check(-5), which triggers the exception because -5 < 0. The exception is caught and its message is printed.

3. Final Answer:

   Negative number not allowed -> Option A

4. Quick Check:

   Exception message printed = C [OK]

Hint: Exception message prints when thrown and caught [OK]

Common Mistakes:

• Expecting the number to print despite exception
• Thinking code causes compilation error
• Ignoring exception catch block

4. Identify the error in the following code snippet that throws a custom exception:

class MyException extends Exception {}

public class Demo {
    public static void test() {
        throw new MyException();
    }
}

medium

A. No error; code is correct.

B. Missing 'throws' declaration in method signature.

C. Incorrect syntax for throwing exception.

D. Cannot extend Exception class.

Solution

1. Step 1: Check method signature for checked exceptions

   Since MyException extends Exception (a checked exception), the method must declare it with throws MyException.

2. Step 2: Identify missing throws declaration

   The method test() throws MyException but does not declare it, causing a compilation error.

3. Final Answer:

   Missing 'throws' declaration in method signature. -> Option B

4. Quick Check:

   Checked exceptions require 'throws' declaration [OK]

Hint: Add 'throws ExceptionName' when throwing checked exceptions [OK]

Common Mistakes:

• Forgetting 'throws' in method signature
• Thinking all exceptions are unchecked
• Assuming extending Exception is invalid

5. You want to create a checked custom exception InvalidAgeException that should be thrown when age is less than 18. Which of the following code snippets correctly defines and throws this exception inside a method validateAge?

hard

A. class InvalidAgeException extends Exception {
public InvalidAgeException() {}
}

void validateAge(int age) {
if (age < 18) throw new InvalidAgeException();
}

B. class InvalidAgeException {
public InvalidAgeException(String msg) { super(msg); }
}

void validateAge(int age) {
if (age < 18) throw new InvalidAgeException("Age must be 18 or older");
}

C. class InvalidAgeException extends RuntimeException {
public InvalidAgeException() {}
}

void validateAge(int age) {
if (age < 18) throw new InvalidAgeException();
}

D. class InvalidAgeException extends Exception {
public InvalidAgeException(String msg) { super(msg); }
}

void validateAge(int age) throws InvalidAgeException {
if (age < 18) throw new InvalidAgeException("Age must be 18 or older");
}

Solution

1. Step 1: Define a checked exception with message constructor

   class InvalidAgeException extends Exception { public InvalidAgeException(String msg) { super(msg); } } void validateAge(int age) throws InvalidAgeException { if (age < 18) throw new InvalidAgeException("Age must be 18 or older"); } correctly extends Exception and defines a constructor that accepts a message, calling super(msg).

2. Step 2: Throw exception with message and declare it

   The method validateAge throws InvalidAgeException when age < 18 and declares it with throws InvalidAgeException.

3. Final Answer:

   class InvalidAgeException extends Exception { public InvalidAgeException(String msg) { super(msg); } } void validateAge(int age) throws InvalidAgeException { if (age < 18) throw new InvalidAgeException("Age must be 18 or older"); } -> Option D

4. Quick Check:

   Checked exception needs constructor, throw, and throws declaration [OK]

Hint: Checked exceptions need constructor, throw, and throws declaration [OK]

Common Mistakes:

• Not extending Exception for checked exceptions
• Missing throws declaration in method
• Not calling super(message) in constructor