Exception other than RuntimeException

by

Yes, there are Three kinds.

Checked exceptions

The compiler will let you know when they can possible be thrown, due to a failure in the environment most likely.

They should be caught, if the program can do something with it, otherwise it is preferred to let them go.

Most of them inherit from 

java.lang.Exception

or from 

java.lang.Throwable

Although it is better to inherit from the former.

For example:

java.io.IOException

Signals that an I/O exception of some sort has occurred. This class is the general class of exceptions produced by failed or interrupted I/O operations.

Errors

These are special kinds of exceptions. They SHOULD NOT BE CAUGHT for when they occur means that something really really bad just happened.

All of them inherit from 

java.lang.Error

For example:

java.lang.OutOfMemoryError

Thrown when the Java Virtual Machine cannot allocate an object because it is out of memory, and no more memory could be made available by the garbage collector.

or 

java.lang.StackOverflowError

Thrown when a stack overflow occurs because an application recurses too deeply.

RuntimeExceptions

Used to identify programmer failures, rather than resource failures.

A Runtime exception could “normally” be avoided while coding. If you have one most likely you’re doing something wrong.

Sometimes runtime exceptions are caught, but, unless you know exactly what you’re doing and why, catching them is a bad practice ( again, unless that’s exactly what you need )

They inherit from 

java.lang.RuntimeException

For example

java.lang.ArrayIndexOutOfBoundsException

Thrown to indicate that an array has been accessed with an illegal index. The index is either negative or greater than or equal to the size of the array

or

java.lang.NullPointerException

Thrown when an application attempts to use null in a case where an object is required

About the last two, MOST of the times, they can be avoided by programming carefully and understand what the state of the program is ( does this array have 5 elements? why should I try to access -1 or 6th. Is this reference null? why should I call null.toString() )

Although I have had arguments with guys that claim that all NPE should be caught. Well what can I say.

More Related Contents:

  1. How can I solve “java.lang.NoClassDefFoundError”?
  2. How do you assert that a certain exception is thrown in JUnit 4 tests?
  3. What are the effects of exceptions on performance in Java?
  4. How to generate exceptions from RepaintManager
  5. Why do I get “Exception; must be caught or declared to be thrown” when I try to compile my Java code?
  6. ClassNotFoundException com.mysql.jdbc.Driver [duplicate]
  7. How to create custom exceptions in Java? [closed]
  8. Given final block not properly padded
  9. Null check chain vs catching NullPointerException
  10. When should we create our own Java exception classes? [closed]
  11. How to test that no exception is thrown?
  12. Using Joda Date & Time API to parse multiple formats
  13. How to create a custom exception type in Java? [duplicate]
  14. Why are Exceptions not Checked in .NET?
  15. Java: Exceptions as control flow?
  16. Closing a Scanner throws java.util.NoSuchElementException
  17. “NoClassDefFoundError: Could not initialize class” error
  18. What is a suppressed exception?
  19. In a Java 7 multicatch block what is the type of the caught exception?
  20. What are reasons for Exceptions not to be compatible with throws clauses?
  21. In Java how can I validate a thrown exception with JUnit?
  22. The throws keyword for exceptions in Java
  23. Android exception handling best practice?
  24. What is meant by abstract=”true” in spring?
  25. Should java try blocks be scoped as tightly as possible?
  26. Should methods that throw RuntimeException indicate it in method signature?
  27. Unable to run JUnit test with PowerMockRunner
  28. Is it possible to detect if an exception occurred before I entered a finally block?
  29. maximum size of java class / exception table
  30. Close resource quietly using try-with-resources

Leave a Comment