Error vs Exception in java


Error vs Exception



An Error "indicates serious problems that a reasonable application should not try to catch."
while
An Exception "indicates conditions that a reasonable application might want to catch."

Error and Exception both are extending Throwable but usually Error is thrown by JVM in a scenario which is fatal and it is not possible for the application to recover from that error. For instance OutOfMemoryError. Even application can raise an Error but its just not a good practice. Application should use checked exceptions for recoverable conditions and runtime exceptions for programming errors.Error is something that most of the time you cannot handle it but exception was meant to give you an opportunity to do something with it. like try something else or write to the log.

Exception is generally divided into two categories e.g. checked and unchecked Exceptions.

1.    Checked Exception has special place in Java programming language and require a mandatory try catch finally code block to handle it.
2.    On the other hand Unchecked Exception, which are subclass of RuntimeException mostly represent programming errors. Most common example of unchecked exception is NullPointerException in Java. 

Checked exceptions are the those from which a program can be recovered programmatically. Examples include FileNotFoundException, ParseException, etc.
A programmer is expected to check for these exceptions by using the try-catch block or throw it back to the caller. On the other-hand we have unchecked exceptions. These are those exceptions that might not happen if everything is in order, but they do occur. Examples include ArrayIndexOutOfBoundException, ClassCastException, etc.

Many applications will use try-catchor throws clause for RuntimeExceptions & their subclasses but from the language perspective it is not required to do so.

Errors are also unchecked exception & the programmer is not required to do anything with these. In fact it is a bad idea to use a try-catch clause for Errors. Most often, recovery from an Error is not possible & the program should be allowed to terminate. Examples include OutOfMemoryError, StackOverflowError etc. Errors can not handled by programmers because even if you catch them you can not recover from them like during OutOfMemoryError, if you catch it you will get it again because Garbage Collector may not be able to free memory in first place. On the other hand Exception can be caught and handled properly.

 If you still have any question you can reach me any time through email (jigyasu2010@hotmail.com)

Comments

Post a Comment

Popular posts from this blog

How Method Overloading Helping in Java - Part 9

I'm sharing my experience with you as these are the questions which have been asked to me while interviewing on java profile. Where have u observed method overloading helped us in java? Where have you seen in java default classes using method overloading? We need method overloading because if we have multiple arguments for add method and we have to create multiple methods in that case we will be confused which method to call to perform specific addition. Example: class   PrintOverloading1 {      public   void  show( char  c)     {           System . out .println(c);     }      public   void  show( char  c,  int  number)      {           System . out .println(c +  " " + number);     }    public   void  show( char  c,  String s )      {           System . out .println(c +  " " + s);     } } class   demo1 {     public   static   void  main( String  args[])    {         PrintOverloading1 obj  =  new   PrintOv
Read more

Design Patterns -- part 1

Design patterns are the best practices used by Developers while working on project. These give design level solutions for recurring problems that software engineers come across often. This helps developers to tackle these problems and design a solution well using patterns. These patterns help other developers so that they do not need to waste time in those problems which were faced by those developers.  What is   Gang Of Four (GOF)? There is a band called Gang Of Four (band) but here we will not be talking about band. We will talk about the authors of Gang of Four design patterns. In 1994, four authors Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides published a book titled Design Patterns - Elements of Reusable Object-Oriented Software Source:  Wikipedia Patterns are formalized  best practices  that the programmer can use to solve common problems when designing an application or system. Object-oriented  design patterns typically show relationships and  interactions
Read more

Access Modifiers in java

Access Modifiers in Java Access to classes is controlled using Access Modifiers aka ( Access Specifiers, Visibility Specifiers ) in java. These are used to regulate access to classes, fields and methods in java. Using access modifiers you can control the access of variables, methods with in a class. Java provides number of access modifiers to control the access for class as well as the fields, methods and constructors in your classes. We have 4 types of access modifiers in java which are explained below:- Default: Visible to the package, the default. No modifiers are needed, no keyword is required. Private: Visible to the class only. Public: Visible to the world. Protected: Visible to the package and all subclasses. Default: We do not have any default specifier in Java. It provides Default specifier which is used where no access modifier is present. Using this you can access class, methods or fields which belongs to same package, but not from outside
Read more