Kotlinlearncs.online LogoJava

    ← Prev

    Index

    Next →

    Kotlin
    Java

    • Using Interfaces : 39

    • Working with Exceptions : 38

    • Throwing Exceptions : 37

    • Catching Exceptions : 36

    • References and Polymorphism : 35

    • References : 34

    • Data Modeling 2 : 33

    • Equality and Object Copying : 32

    • Polymorphism : 31

    • Inheritance : 30

    • Data Modeling 1 : 29

    • Static : 28

    • Encapsulation : 27

    • Constructors : 26

    • Objects, Continued : 25

    • Introduction to Objects : 24

    • Compilation and Type Inference : 23

    • Practice with Collections : 22

    • Maps and Sets : 21

    • Lists and Type Parameters : 20

    • Imports and Libraries : 19

    • Multidimensional Arrays : 18

    • Practice with Strings : 17

    • null : 16

    • Algorithms and Strings : 15

    • Strings : 14

    • Functions and Algorithms : 13

    • Practice with Functions : 12

    • More About Functions : 11

    • Errors and Debugging : 10

    • Functions : 9

    • Practice with Loops and Algorithms : 8

    • Algorithms I : 7

    • Loops : 6

    • Arrays : 5

    • Compound Conditionals : 4

    • Conditional Expressions and Statements : 3

    • Operations on Variables : 2

    • Variables and Types : 1

    • Hello, world! : 0

    Working with Exceptions

    public class MyException extends Exception { }
    boolean youAreAlone = false;
    if (youAreAlone) {
    throw new MyException("You are not alone!");
    }

    In this lesson we’ll focus on how to use Java’s exception handling mechanisms—both try-catch and throw. We’ll also introduce a few new wrinkles to round out our understanding of this particular system. Our focus is on real-word patterns for working with and handling errors.

    Warm Up Debugging Challenge
    Warm Up Debugging Challenge

    But! Let’s warm up with another debugging challenge!

    Re-throw and finally
    Re-throw and finally

    Before we go on, let’s look at a few further wrinkles in Java exception handling that we haven’t touched on yet.

    Re-throw
    Re-throw

    First, you may have wondered: what happens if you throw an exception inside a catch block? Let’s try it:

    try {
    throw new Exception("Try");
    } catch (Exception e) {
    throw new Exception("Catch");
    }

    You’ll notice that the second exception is thrown out of the catch block. Of course, we can rewrap the entire try-catch in another try-catch:

    try {
    try {
    throw new Exception("Try");
    } catch (Exception e) {
    throw new Exception("Catch");
    }
    } catch (Exception e) {
    System.out.println("Caught it! " + e);
    }

    Note that exceptions thrown inside a catch block cannot be caught by the same try-catch in which they were thrown. So this doesn’t work:

    try {
    throw new IllegalStateException("Try");
    } catch (IllegalStateException e) {
    throw new IllegalArgumentException("Nope");
    } catch (IllegalArgumentException e) {
    System.out.println("Won't get here");
    }

    finally
    finally

    try-catch blocks can include an additional component: a finally block. The finally block is always executed, regardless of whether an exception was thrown or not. Let’s see how that works:

    import java.util.Random;
    Random random = new Random();
    try {
    if (random.nextBoolean()) {
    throw new Exception();
    }
    System.out.println("Try");
    } catch (Exception e) {
    System.out.println("Catch");
    } finally {
    System.out.println("Finally");
    }
    System.out.println("Done");

    If you run this a few times, you’ll notice that regardless of whether we complete the try block successfully or enter the catch, the finally block is always executed.

    One of the cool things about finally is that it is always executed. Even if the try includes a return!

    int example() {
    try {
    return 0;
    } finally {
    System.out.println("Done");
    }
    }
    System.out.println(example());

    This feature of finally makes it useful when a method needs to do some kind of cleanup before exiting. We haven’t run into this scenario yet, but you will sometimes. And when you do, finally will be there for you!

    Practice: PingPonger Class

    Created By: Geoffrey Challen
    / Version: 2020.11.0

    Create a public class PingPonger. A PingPonger is in one of two states: ping or pong. You should provide a constructor accepting a String argument that sets the initial state. If the passed String is "ping", the initial state is ping. If the passed String is "pong", the initial state is pong. If the passed String is not ping or pong, you should throw an IllegalArgumentException.

    Once the PingPonger has been created, the user should call pong if the state is ping and ping if the state is pong. ping takes no arguments and returns true. pong takes no arguments and returns false. If ping or pong is called out of order, you should throw an IllegalStateException.

    Here's an example:

    Exception Handling Patterns
    Exception Handling Patterns

    Next let’s look at a few common exception handling patterns.

    Why Not assert?
    Why Not assert?

    Previously we’ve presented how to handle bad inputs using assert:

    void doIt(String it) {
    assert it != null : "That's not it!";
    System.out.println(it);
    }
    doIt("Good!");
    doIt(null);

    But here’s the dirty truth about Java assertions: they are not on by default! If you examine the Java command line options you’ll see that you need to pass a special flag to java to turn assertions on. Let’s look at how that works in practice in a brief screencast:

    assert is enabled in all of our playgrounds. However, in other Java environments—such as on Android—it may be hard or impossible to enable assertions. While they can be useful during testing, the right thing to do in most cases is to throw an Exception rather than rely on assert.

    Input Validation
    Input Validation

    However, we can replace many of the places where we had previously used assert with commonly available non-checked Java exceptions. When checking parameters to a method, IllegalArgumentException is usually what you want to use:

    void doIt(String it) {
    if (it == null) {
    throw new IllegalArgumentException("That's not it!");
    }
    }
    doIt("Good!");
    doIt(null);

    Note that because IllegalArgumentException is unchecked, you don’t need to use throws to declare that the method throws it. And the compiler will not require that you catch it. This is good, since usually an IllegalArgumentException indicates that the inputs to a method contradict the documentation.

    State Validation
    State Validation

    When designing our Java classes, there are times when we want to enforce patterns of usage that span multiple methods. To make that more concrete, let’s look at an example together:

    // State Validation Example

    Batching Failures
    Batching Failures

    Sometimes our code needs to take a series of steps to complete some action. If any of those steps fail, the entire operation fails. This can be a good place to use a try-catch to avoid having to do a lot of error checking after each step. Let’s look at an example of this:

    import com.fasterxml.jackson.databind.ObjectMapper;
    import com.fasterxml.jackson.databind.JsonNode;
    ObjectMapper mapper = new ObjectMapper();
    String json = """
    {
    "you": {
    "are": {
    "not": {
    "alone": true
    }
    }
    }
    }
    """;
    JsonNode node = mapper.readTree(json);

    Rethrowing Exceptions
    Rethrowing Exceptions

    Sometimes when an error occurs we just want to log that it happened, but then let it continue to propagate. We can do this by rethrowing the error out of the catch block:

    try {
    throw new Exception("Had a problem");
    } catch (Exception e) {
    System.out.println("Had a problem: " + e);
    throw e;
    }

    You can also use this technique to convert a checked exception to an unchecked exception:

    try {
    throw new Exception("Had a problem");
    } catch (Exception e) {
    System.out.println("Had a problem: " + e);
    throw new IllegalStateException(e);
    }

    Why would we do this? In some cases, even if the compiler will insist that we “handle” a checked exception, there really isn’t anything reasonable to do other than crash. In that case, converting the checked exception to an unchecked RuntimeException (like IllegalStateException above) simplifies the error handling. Methods that call our method now don’t themselves need to handle the exception, because it is unchecked.

    Designing Your Own Exceptions
    Designing Your Own Exceptions

    Once you start writing your own libraries and sharing code with others, it can be helpful to design your own custom exceptions. One reason to do this is that it allows users of your code to better understand what went wrong. And to do more accurate error handling by establishing multiple catch blocks that deal with different kinds of exceptions.

    Happily, extending Exception could not be easier:

    public class MyNewException extends Exception {}

    Note that this creates a checked exception. Usually that’s what you want, since there is usually a reasonable unchecked exception already available for you. But you can create new unchecked exceptions similarly by extending RuntimeException.

    Homework: Pentagon Shape

    Created By: Geoffrey Challen
    / Version: 2021.10.0

    Create and complete the implementation of the Pentagon class. Your class should be public, inherit from the Shape class, and provide the following methods:

    1. Constructor that takes a double parameter. Creates a new Pentagon with the passed side length. If the passed length is less than or equal to 0, throw an IllegalArgumentException. You should call the Shape constructor and pass it the String "pentagon" to identify the type of this shape.
    2. Public instance method area that takes no arguments and returns a double. Return the area of this shape, given only the side length, which you can find here: https://www.cuemath.com/measurement/area-of-pentagon/. You will need to use Math.sqrt to solve this problem.
    3. Override public boolean equals(Object other). Return true if other is a Pentagon with the same side length, and false otherwise. Note that other may be null or not a Pentagon.

    Finally, note that your class should not expose any of its internal state publicly.

    More Practice

    Need more practice? Head over to the practice page.