First Do No Harm: Deferred Checked Exception Handling Promotes Reliability

Unlike ignoring return codes, ignoring exceptions does not lead to difficult debugging; on the contrary, deferred handling of expected exceptions arises naturally because handlers (1) potentially mask bugs; (2) add to the amount of code being debugged simultaneously; (3) often require a scope outside the method being coded, leading to conflict; and (4) compete for attention with coding the functionality, leading to neglect. Deferred handling overcomes these problems, and after debugging, error coding is the focus of a refactoring.

With Java, deferred checked exception handling is not a natural outcome. This presentation discusses tools and techniques that promote reliability by supporting deferred error handling and its refactoring.

Copyright © 2013 Oracle and/or its affiliates. Oracle® is a registered trademark of Oracle and/or its affiliates. All rights reserved. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the "Materials"). The Materials are provided "as is" without any warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.