Exception Handling

1. Exception Handling Chapter 8

2. Outline • Basic Exception Handling • Defining Exception Classes • Using Exception Classes

3. Introduction • A program can be written assuming that nothing unusual or incorrect will happen. • The user will always enter an integer when prompted to do so. • There will always be a nonempty list for a program that takes an entry from the list. • The file containing the needed information will always exist. • Unfortunately, it isn’t always so.

4. Introduction, cont. • Once the core program is written for the usual, expected case(s), Java’s exception-handling facilities should be added to accommodate the unusual, unexpected case(s).

5. Introduction, cont. • Exception handling divides a class or method definition into separate sections: • one section for the normal case(s) • another section for the exceptional case(s). • Depending on how a method is used, special cases may need to be handled in different ways. • Sometimes an exception needs to be thrown to handle a problem outside the method.

6. Basic Exception Handling: Outline • Exceptions in Java • Predefined Exception Classes

7. Exception Handling • Either your code or Java signals when something unusual happens. • The signaling process is called throwing an exception. • Somewhere in your program, you can place code to handle the exception.

8. Exceptions in Java: Example • simple example • Suppose the students are hosting an event to express appreciation to their professor, at which donuts and milk will be served. • If the number of donuts is known, and the number of glasses of milk is known, it should be possible to calculate the number of donuts per class of milk.

9. Exceptions in Java: Example, cont. • simple example, cont. • But what if there is no milk because the cows are on strike? • An attempt to divide the number of donuts by the number of glasses of milk will result in an attempt to divide by zero. • This would be an utter (udder?) disaster, known in Java as an exception.

10. Exceptions in Java: Example, cont. • In Java, it is possible to test for this unusual situation using an if-else statement, for example.

11. Exceptions in Java: Example, cont.

12. Exceptions in Java: Example, cont. • In Java, it is also possible to throw an exception.

13. Exceptions in Java: Example, cont.

14. Exceptions in Java • Exceptions are handled using atry-throw-catchthreesome. • tryblock syntax try { Code_to_Try Throw_An_Exception_Or_Invoke_A_Method _That_Might_Throw_An_Exception Possibly_More_Code }

15. Exceptions in Java, cont. • Exception is a predefined class. • The throw statement creates a new object of the class Exception and throws it. throw new Exception (“Exception: No Milk!); • When an exception is thrown, control transfers from the try block to a catch block, and is called catching the exception.

16. throw Statement and catch Block • throw statement syntax throw new Exception_Class_Name (Quoted_String_Argument); • Quoted_String_Argument is passed to the constructor for classException which stores it in the instance variable of the Exception object.

17. throw Statement and catch Block, cont. • catch block syntax catch(Exception e) { Code_To_Be_Performed { • eis called thecatch-block parameter.

18. The catch Block • The class name preceding the catch-block parameter specifies what kind of exception the catch block can catch. • Class name Exception permits any exception to be caught. • The catch-block parameter provides a name for the exception that is caught, to permit the exception object to be used subsequently. • If the program cannot recover from the exception, the catch block can include System.exit(0);

19. method getMessage • Every exception has a method called getMessage. • By default, this method retrieves the string given to the constructor of the exception object.

20. method getMessage, cont. • Flow of Control - no exception is thrown

21. method getMessage, cont. • Flow of Control - an exception is thrown

22. try-throw-catch • The try-throw-catch threesome is similar to an if-else statement. • However, an object of the class Exception is created and its message can be carried by the thrown exception, providing more versatility than an if-else statement

23. Predefined Exception Classes • Some methods in predefined classes can throw predefined exceptions. • An invocation of such a predefined method can be included in a try block and followed by a catch block. • some predefined exceptions: • IOException • ClassNotFoundException • FileNotFoundException

24. Predefined Exception Classes, cont. • Class Exception is the root class of all exceptions. • However, an exception typically is handled more appropriately by one of its descendants. • The string returned by a predefined exception typically provides enough information to identify the source of the exception.

25. ArrayOutOfBoundsException • When a program attempts to use an array index that is out of bounds, an ArrayOutOfBoundsException is thrown. • The program ends unless the exception is caught in a catch block. • An ArrayOutOfBoundsException usually indicates a code error rather than an exception that should be caught.

26. Defining Exception Classes • You can define your own exception classes, but they must be derived from an existing exception class. • Constructors are the most important, and often the only methods (except for methods inherited from the base class).

27. Defining Exception Classes, cont.

28. Defining Exception Classes, cont.

29. Java Tip: Preserve getMessage • For all predefined exception classes, method getMessage returns either • the string that is passed as an argument to the constructor or • a default string if no argument is passed to the constructor. • The behavior of method getMessage should be preserved in any exception class you define.

30. Java Tip: Preserve getMessage, cont. • This is done by including a string parameter that begins with a call to super. public MyException(String message) { super(message); More_Code_If_Appropriate } • Also include a default constructor. public MyException() { super(“MyException thrown”); More_Code_If_Appropriate }

31. Programming Tip: When to Define an Exception Class • In general, define an exception class if you are going to insert a throw statement in your code. • This permits catch blocks to distinguish between your exceptions and exceptions thrown by predefined methods.

32. Guidelines • Use class Exception as the base class unless there is a compelling reason to do otherwise. • Define at least two constructors. Typically, no other methods are needed. • Begin each constructor definition with a call to the constructor of the base class.

33. Guidelines, cont. • Include a default constructor in which the call to super has a string argument indicating the kind of exception. • The string can be recovered using the getMessage method. • Include a constructor that takes a single string argument used in the call to super. • The string can be recovered with a call to getMessage.

34. Using Exception Classes: Outline • Declaring Exceptions (Passing the Buck) • Exceptions That Need Not Be Caught • Multiple Throws and Catches • (optional) The finally Block • (optional) Rethrowing an Exception

35. Declaring Exceptions (Passing the Buck) • Sometimes is it appropriate to handle an exception other than in the method where the exception occurred. • For example, it might be better to handle the exception in the method that called the method that called the method… that threw the exception

36. Declaring Exceptions, cont. • If a method can throw an exception but does not catch it, it must alert the programmer to the possibility of an exception by including a throws clause. • Example public void someMethod() throws DivideByZeroException

37. Accounting for Exceptions • An exception can be caught in a catch block within a method definition. • Alternatively, the possibility of an exception can be declared at the start of the method definition by placing the exception-class name in a throws clause. • These two approaches can be mixed in a method, catching some exceptions and declaring others in a throws clause.

38. Accounting for Exceptions, cont. • If method_A uses a throws clause instead of handling an exception and method_B calls method_A, then method_B either must handle the exception or must also include a throws clause.

39. Accounting for Exceptions, cont.

40. Accounting for Exceptions, cont. • A throws clause can include more than one exception type. • example public int someMethod()throws IOException, DivideByZeroException • Some method in the calling hierarchy should handle the exception. • If an exception is thrown, but never caught, either the program terminates or its behavior becomes unreliable.

41. Exceptions That Need Not Be Caught • Some exceptions do not need to be accounted for in any way. • (Perhaps these are the exceptions that prove the rule about needing to account for exceptions.) • Exceptions that do not need to be accounted for result from errors and usually are thrown by methods in predefined classes.

42. Exceptions That Need Not Be Caught, cont. • “Exceptions” that derive from the class Error or the class RunTimeException do not need to be accounted for. • examples • NoSuchMethodError • OutOfMemoryError • Adding a catch clause or “passing the buck” will not solve the problem.

43. Exceptions That Need Not Be Caught, cont. • In the event you fail to account for some exception that Java requires you to account for, the compiler will alert you.

44. throws Clauses in Derived Classes • When a method is redefined in a derived class, the redefined method cannot contain any exception classes that are not in the throws clause of the same method in the base class (though the derived class can list fewer exceptions in its throws clause). • Any exceptions thrown in the derived class must be caught or thrown by the base class.

45. Multiple Throws and Catches • A try block can throw any number of different types of exceptions. • Each catch block can catch only one type of exception. • Multiple catch blocks after a try block can catch multiple types of exceptions.

46. Multiple Throws and Catches, cont.

47. Multiple Throws and Catches, cont. • class NegativeNumbersException

48. Java Tip: Catch the More Specific Exceptions First • catch blocks are examined in order. • The first matching catch block is executed. • More specific exceptions should precede less specific exceptions, i.e. exceptions lower in the exception hierarchy should come before exceptions higher in the exception hierarchy.

49. Keep It Simple • Attempt to modify a program or class definition so that it does now need a throw statement. • In general, use exceptions sparingly. • If the way the exception is handled depends on the calling method, let the calling method handle the exception. • Consider throwing the exception and catching the exception in separate methods.

50. Keep It Simple, cont. public void methodB() { ... try { ... methodA(); ... } catch (MyException e) ...