Throws keyword in Java - Step-by-Step Execution

Concept Flow - Throws keyword

Method Declaration

↓

Add 'throws' keyword with Exception

↓

Method Call

↓

Caller handles Exception

↓

Try-Catch or throws further

↓

Program continues or terminates

The throws keyword declares that a method might throw an exception, so callers must handle or declare it.

Execution Sample

Java

public void readFile() throws IOException {
    FileReader file = new FileReader("file.txt");
    file.read();
    file.close();
}

This method declares it throws IOException, so callers must handle or declare this exception.

Execution Table

Step	Action	Evaluation	Result
1	Call readFile()	Method declared with throws IOException	Caller must handle IOException
2	Inside readFile(), create FileReader	FileReader("file.txt")	May throw IOException if file missing
3	Call file.read()	Reads file content	May throw IOException
4	Call file.close()	Close file stream	May throw IOException
5	If IOException occurs	Exception thrown	Caller must catch or declare
6	Caller uses try-catch	Catch IOException	Handle exception gracefully
7	If no exception	Method completes	Program continues normally

💡 Execution stops if IOException is thrown and not caught; otherwise continues after method call

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
file	null	FileReader object created	FileReader reading	FileReader closed	null or eligible for GC

Key Moments - 3 Insights

Why do we need the throws keyword in the method declaration?

Because the method uses code that can cause checked exceptions (like IOException), the throws keyword tells callers they must handle or declare these exceptions, as shown in execution_table step 1.

What happens if the caller does not handle the exception declared by throws?

The program will not compile. The caller must either catch the exception in a try-catch block or declare it with throws, as explained in execution_table steps 5 and 6.

Does the throws keyword handle the exception inside the method?

No, throws only declares the possibility of an exception. Handling must be done by the caller or inside the method with try-catch. This is clear from execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what must the caller do at step 1 when calling readFile()?

A Handle or declare IOException

B Ignore the exception

C Catch RuntimeException

D Close the file manually

💡 Hint

Refer to execution_table row 1 about caller responsibility

At which step does the IOException possibly get thrown inside readFile()?

A Step 5

B Step 4

C Step 2

D Step 7

💡 Hint

Check execution_table rows 2, 3, and 4 about exception throwing

If the caller does not catch IOException, what happens according to the execution flow?

A Program compiles but throws runtime error

B Program fails to compile

C Program compiles and runs normally

D Exception is ignored silently

💡 Hint

See key_moments answer 2 and execution_table step 5

Concept Snapshot

Throws keyword in Java:
- Declares a method may throw checked exceptions
- Syntax: method() throws ExceptionType
- Caller must handle or declare the exception
- Does not catch exceptions, only signals them
- Used for checked exceptions like IOException

Full Transcript

The throws keyword in Java is used in method declarations to indicate that the method might throw certain checked exceptions, such as IOException. When a method declares throws, any code calling that method must either handle the exception with a try-catch block or declare it further with throws. This ensures that exceptions are properly managed and the program can handle error situations gracefully. The method itself does not handle the exception; it only signals the caller about the possibility. If the caller ignores this requirement, the program will not compile. This flow helps keep Java programs safe and predictable when dealing with errors.

Practice

1.

What is the main purpose of the throws keyword in Java?

easy

A. To declare that a method might throw certain checked exceptions

B. To catch exceptions inside a method

C. To create a new exception object

D. To stop the program immediately when an error occurs

Solution

1. Step 1: Understand the role of throws

   The throws keyword is used in a method signature to declare that the method might throw certain checked exceptions.

2. Step 2: Differentiate from other keywords

   It does not catch exceptions (that's try-catch), nor create exceptions or stop the program immediately.

3. Final Answer:

   To declare that a method might throw certain checked exceptions -> Option A

4. Quick Check:

   throws declares exceptions [OK]

Hint: Remember: throws declares, catch handles exceptions [OK]

Common Mistakes:

• Confusing throws with catch
• Thinking throws creates exceptions
• Believing throws stops program immediately

2.

Which of the following is the correct way to declare a method that might throw an IOException?

public void readFile() _____ IOException { }

easy

A. thrown

B. throw

C. throws

D. throws new

Solution

1. Step 1: Recall correct syntax for exception declaration

   In Java, the keyword to declare exceptions a method might throw is throws.

2. Step 2: Check options for syntax correctness

   throw is used to actually throw an exception inside method body, not in declaration. thrown and throws new are invalid.

3. Final Answer:

   throws -> Option C

4. Quick Check:

   Method declaration uses throws [OK]

Hint: Method declarations use 'throws', not 'throw' [OK]

Common Mistakes:

• Using 'throw' instead of 'throws' in method signature
• Adding 'new' after throws
• Using non-existent keywords like 'thrown'

3.

What will be the output of the following code?

import java.io.*;

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

medium

A. Error happened

B. Compilation error due to missing throws

C. No output

D. Runtime error without message

Solution

1. Step 1: Analyze method throwing exception

   The method risky() declares it throws IOException and actually throws it with message "Error happened".

2. Step 2: Check exception handling in main

   The main method calls risky() inside a try block and catches IOException, printing the exception message.

3. Final Answer:

   Error happened -> Option A

4. Quick Check:

   Exception caught and message printed [OK]

Hint: Thrown exceptions must be caught or declared [OK]

Common Mistakes:

• Thinking throws causes compile error if caught
• Expecting no output because exception thrown
• Confusing throws with throw inside method body

4.

Identify the error in the following code snippet:

public void process() {
    riskyMethod() throws IOException;
}

medium

A. Incorrect use of throws keyword inside method body

B. Missing try-catch block around riskyMethod() call

C. Method process() should declare throws IOException

D. All of the above

Solution

1. Step 1: Check syntax of throws usage

   The throws keyword cannot be used inside a method body; it belongs in the method signature.

2. Step 2: Analyze exception handling requirements

   Calling riskyMethod() which throws IOException requires either a try-catch block or declaring throws IOException in process().

3. Step 3: Combine all errors

   All these issues are present: wrong throws usage, missing try-catch, and missing throws declaration.

4. Final Answer:

   All of the above -> Option D

5. Quick Check:

   Throws only in signature + handle exceptions [OK]

Hint: Throws keyword only in method signature, not inside body [OK]

Common Mistakes:

• Using throws inside method body
• Not handling checked exceptions properly
• Forgetting to declare throws in method signature

5.

You have a method readData() that calls two other methods: openFile() and parseFile(). Both can throw IOException. How should you declare readData() to properly handle exceptions?

hard

A. Do nothing, exceptions will be handled automatically

B. Declare readData() with throws IOException and let caller handle it

C. Declare readData() with throws Exception to cover all exceptions

D. Use try-catch inside readData() to catch and ignore exceptions

Solution

1. Step 1: Understand exception propagation

   If openFile() and parseFile() throw IOException, readData() must either handle or declare these exceptions.

2. Step 2: Choose proper declaration

   Declaring throws IOException in readData() lets the caller decide how to handle exceptions, keeping code clean and clear.

3. Step 3: Evaluate other options

   Ignoring exceptions is bad practice. Declaring throws Exception is too broad. Exceptions are not handled automatically.

4. Final Answer:

   Declare readData() with throws IOException and let caller handle it -> Option B

5. Quick Check:

   Declare checked exceptions to propagate [OK]

Hint: Declare throws for checked exceptions to pass responsibility [OK]

Common Mistakes:

• Ignoring exceptions instead of declaring or catching
• Declaring too broad exceptions like Exception
• Assuming exceptions are handled automatically