An exception is a
problem that arises during the execution of a program. An exception can occur
for many different reasons, including the following:
·
A user has entered invalid data.
·
A file that needs to be opened cannot be found.
·
A network connection has been lost in the middle of communications, or
the JVM has run out of memory.
Some of these
exceptions are caused by user error, others by programmer error, and others by
physical resources that have failed in some manner.
To understand how
exception handling works in Java, you need to understand the three categories
of exceptions:
·
Checked exceptions: A checked
exception is an exception that is typically a user error or a problem that
cannot be foreseen by the programmer. For example, if a file is to be opened,
but the file cannot be found, an exception occurs. These exceptions cannot
simply be ignored at the time of compilation.
·
Runtime exceptions: A runtime
exception is an exception that occurs that probably could have been avoided by
the programmer. As opposed to checked exceptions, runtime exceptions are
ignored at the time of compliation.
·
Errors: These are not exceptions at all,
but problems that arise beyond the control of the user or the programmer.
Errors are typically ignored in your code because you can rarely do anything
about an error. For example, if a stack overflow occurs, an error will arise.
They are also ignored at the time of compilation.
Exception Hierarchy:
All exception classes
are subtypes of the java.lang.Exception class. The exception class is a
subclass of the Throwable class. Other than the exception class there is
another subclass called Error which is derived from the Throwable class.
Errors are not
normally trapped form the Java programs. These conditions normally happen in
case of severe failures, which are not handled by the java programs. Errors are
generated to indicate errors generated by the runtime environment. Example :
JVM is out of Memory. Normally programs cannot recover from errors.
The Exception class
has two main subclasses : IOException class and RuntimeException Class.
An exception is a
problem that arises during the execution of a program. An exception can occur
for many different reasons, including the following:
·
A user has entered invalid data.
·
A file that needs to be opened cannot be found.
·
A network connection has been lost in the middle of communications, or
the JVM has run out of memory.
Some of these
exceptions are caused by user error, others by programmer error, and others by
physical resources that have failed in some manner.
To understand how
exception handling works in Java, you need to understand the three categories
of exceptions:
·
Checked exceptions: A checked
exception is an exception that is typically a user error or a problem that
cannot be foreseen by the programmer. For example, if a file is to be opened,
but the file cannot be found, an exception occurs. These exceptions cannot
simply be ignored at the time of compilation.
·
Runtime exceptions: A runtime
exception is an exception that occurs that probably could have been avoided by
the programmer. As opposed to checked exceptions, runtime exceptions are
ignored at the time of compliation.
·
Errors: These are not exceptions at all,
but problems that arise beyond the control of the user or the programmer.
Errors are typically ignored in your code because you can rarely do anything
about an error. For example, if a stack overflow occurs, an error will arise.
They are also ignored at the time of compilation.
Exception Hierarchy:
All exception classes
are subtypes of the java.lang.Exception class. The exception class is a
subclass of the Throwable class. Other than the exception class there is
another subclass called Error which is derived from the Throwable class.
Errors are not
normally trapped form the Java programs. These conditions normally happen in
case of severe failures, which are not handled by the java programs. Errors are
generated to indicate errors generated by the runtime environment. Example :
JVM is out of Memory. Normally programs cannot recover from errors.
The Exception class
has two main subclasses : IOException class and RuntimeException Class.
Life cycle of Exception handling:
```````````````````````````````````````
- Try
- Throw
- Throws
- catch
- Finally
Exceptions:
``````````````
- Arithmatic Exception
- ArrayIndexOfBounds Exception
- IllegalArgument Exception
- NumberFormat Exception
- NullPointer Exception
- StackOverflow Error
- NoClassDefFound Error
No comments:
Post a Comment