In this lesson we’ll focus on how to use Java’s exception handling mechanisms—both
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.
But! Let’s warm up with another debugging challenge!
Create a public class called
You should expose two public methods:
add: adds a value, does not return a value
last: returns an array containing the last 8 values that were added, in any order.
You do not need a constructor, but you can add an empty one if you need. Until 8 values have been added you should return 0s in their place.
For example, here's how an instance of
Last8 should work:
Do not create a huge array to save the values. Submissions that do will be marked incorrect.
Before we go on, let’s look at a few further wrinkles in Java exception handling that we haven’t touched on yet.
First, you may have wondered: what happens if you throw an exception inside a
Let’s try it:
You’ll notice that the second exception is thrown out of the
Of course, we can rewrap the entire
try-catch in another
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-catch blocks can include an additional component: a
finally block is always executed, regardless of whether an exception was thrown or not.
Let’s see how that works:
If you run this a few times, you’ll notice that regardless of whether we complete the
try block successfully or enter 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
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!
Create a public class
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
PingPonger has been created, the user should call
pong if the state is ping
ping if the state is pong.
ping takes no arguments and returns
pong takes no arguments
pong is called out of order, you should throw an
Here's an example:
Next let’s look at a few common exception handling patterns.
Previously we’ve presented how to handle bad inputs using
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
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:
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.
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:
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:
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:
You can also use this technique to convert a checked exception to an unchecked exception:
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
IllegalStateException above) simplifies the error handling.
Methods that call our method now don’t themselves need to handle the exception, because it is unchecked.
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.
Exception could not be easier:
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
Create and complete the implementation of the
Your class should be public, inherit from the
Shape class, and provide the following methods:
doubleparameter. Creates a new
Pentagonwith the passed side length. If the passed length is less than or equal to 0, throw an
IllegalArgumentException. You should call the
Shapeconstructor and pass it the
String"pentagon" to identify the type of this shape.
areathat 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.sqrtto solve this problem.
public boolean equals(Object other). Return
Pentagonwith the same side length, and
falseotherwise. Note that
nullor not a
Finally, note that your class should not expose any of its internal state publicly.
Need more practice? Head over to the practice page.