Difference between revisions of "Java Exception Handling"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 17: Line 17:
=== When catching exceptions, log appropriately ===
=== When catching exceptions, log appropriately ===


=== Between modules, throw only generic exceptions (e.g. java.lang.Exception, java.lang.RuntimeException) ===
=== Between modules, throw only generic exceptions (e.g. java.lang.Exception, java.lang.RuntimeException) without cause ===

Revision as of 15:58, 17 September 2008

Problem description

Modules need dependencies of other modules only because of their exception classes

Stacktraces are sometimes swallowed

Sometimes, excessive stacktraces are shown, even without useful information

Logger.error, System.out and e.printStackTrace are mixed up happily

No distinction between exceptions and errors

Conclusion

Distinguish between errors and exceptions

Inside a module, always throw errors up as they are

When catching exceptions, log appropriately

Between modules, throw only generic exceptions (e.g. java.lang.Exception, java.lang.RuntimeException) without cause

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Java_Exception_Handling&oldid=21217"