If the code in a method can potentially throw a checked exception, then that method must

Valid Java programming language code must honor the Catch or Specify Requirement. This means that code that might throw certain exceptions must be enclosed by either of the following:

  • A try statement that catches the exception. The try must provide a handler for the exception, as described in Catching and Handling Exceptions.
  • A method that specifies that it can throw the exception. The method must provide a throws clause that lists the exception, as described in Specifying the Exceptions Thrown by a Method.

Code that fails to honor the Catch or Specify Requirement will not compile.

Not all exceptions are subject to the Catch or Specify Requirement. To understand why, we need to look at the three basic categories of exceptions, only one of which is subject to the Requirement.

The Three Kinds of Exceptions

The first kind of exception is the checked exception. These are exceptional conditions that a well-written application should anticipate and recover from. For example, suppose an application prompts a user for an input file name, then opens the file by passing the name to the constructor for java.io.FileReader. Normally, the user provides the name of an existing, readable file, so the construction of the FileReader object succeeds, and the execution of the application proceeds normally. But sometimes the user supplies the name of a nonexistent file, and the constructor throws java.io.FileNotFoundException. A well-written program will catch this exception and notify the user of the mistake, possibly prompting for a corrected file name.

Checked exceptions are subject to the Catch or Specify Requirement. All exceptions are checked exceptions, except for those indicated by Error, RuntimeException, and their subclasses.

The second kind of exception is the error. These are exceptional conditions that are external to the application, and that the application usually cannot anticipate or recover from. For example, suppose that an application successfully opens a file for input, but is unable to read the file because of a hardware or system malfunction. The unsuccessful read will throw java.io.IOError. An application might choose to catch this exception, in order to notify the user of the problem — but it also might make sense for the program to print a stack trace and exit.

Errors are not subject to the Catch or Specify Requirement. Errors are those exceptions indicated by Error and its subclasses.

The third kind of exception is the runtime exception. These are exceptional conditions that are internal to the application, and that the application usually cannot anticipate or recover from. These usually indicate programming bugs, such as logic errors or improper use of an API. For example, consider the application described previously that passes a file name to the constructor for FileReader. If a logic error causes a null to be passed to the constructor, the constructor will throw NullPointerException. The application can catch this exception, but it probably makes more sense to eliminate the bug that caused the exception to occur.

Runtime exceptions are not subject to the Catch or Specify Requirement. Runtime exceptions are those indicated by RuntimeException and its subclasses.

Errors and runtime exceptions are collectively known as unchecked exceptions.

Bypassing Catch or Specify

Some programmers consider the Catch or Specify Requirement a serious flaw in the exception mechanism and bypass it by using unchecked exceptions in place of checked exceptions. In general, this is not recommended. The section Unchecked Exceptions — The Controversy talks about when it is appropriate to use unchecked exceptions.

Article 6 of 6

Part of: Troubleshooting common Java errors and exceptions

Just how well do you know exception handling in Java? These 10 tough multiple-choice questions on checked and unchecked exceptions will test your error handling mettle.

Every time software runs, there's a potential for an error to occur that could grind the application to a halt.

The Java programming language provides a number of error-handling constructs that enable the developer to recover from and handle problems that occur at runtime. Some of those constructs include:

  • checked exceptions;
  • runtime exceptions;
  • system level errors; and
  • try, catch, finally blocks.

Think you've got a solid grasp on how to develop effective, error-proof Java code? Take this tough, multiple-choice, Java exception handling quiz and find out.

Next Steps

Developers want improved performance, efficiency in Java 20

Dig Deeper on JSRs and APIs

  • If the code in a method can potentially throw a checked exception, then that method must
    A breakdown of new features in Micronaut 3

    If the code in a method can potentially throw a checked exception, then that method must

    By: Kelly Richardson

  • If the code in a method can potentially throw a checked exception, then that method must
    Java Exception handling best practices

    If the code in a method can potentially throw a checked exception, then that method must

    By: Cameron McKenzie

  • If the code in a method can potentially throw a checked exception, then that method must
    exception handling

    If the code in a method can potentially throw a checked exception, then that method must

    By: Alexander Gillis

  • If the code in a method can potentially throw a checked exception, then that method must
    What are checked vs. unchecked exceptions in Java?

    If the code in a method can potentially throw a checked exception, then that method must

    By: Cameron McKenzie

Part of: Troubleshooting common Java errors and exceptions

Article 6 of 6

When you write a method that throws a checked exception you must?

If some code within a method throws a checked exception, then the method must either handle the exception or it must specify the exception using the throws keyword. In checked exception, there are two types: fully checked and partially checked exceptions.

When an exception is thrown by a method that is executing?

8) When an exception is thrown by a method that is executing under several layers of method calls, a stack trace indicates the method executing when an exception occurred and all of the methods that were called in order to execute that method.

What can a method do with a checked exception quizlet?

Two things a method must do with a checked exception. The method throws the exception to its caller. When an exception is thrown in a try block and there is no matching catch block, this happens. Stream type which provides input from a disk file.

How can you tell if an exception is checked or unchecked?

Difference Between Checked and Unchecked Exceptions in Java A checked exception is caught at compile time whereas a runtime or unchecked exception is, as it states, at runtime. A checked exception must be handled either by re-throwing or with a try catch block, whereas an unchecked isn't required to be handled.