Unchecked, unchecked exceptions and closures

Unchecked exceptions make your code much simpler. For example, the Spring JDBC Template support can shrink your JDBC code enormously by getting rid of those unsightly try, catch, and finally blocks, and cleanly releasing the database resources like connections, statements, etc. Checked exceptions are also the main reason for Java not having closures till JRE 6.0 as it adds to the complexity.

I was reading as above. I have not clearly undertsood it.
please advise
Any links resources ideas highly appreciated. Thanks in advance
LVL 7
gudii9Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Sharon SethConnect With a Mentor Commented:
As you said what you gave above are all unchecked exceptions and you SHOULD not handle them . These exceptions should , in almost all cases , be thrown and cause the application to stop whatever it was doing at that point , Or they should be handled gracefully . Encountering one of those exceptions means you have hit an unexpected situation , which needs to be analysed . On the other hand , if you just handle and ignore those exceptions , then you it means a possible bug in the system goes uncaught/ignored.
0
 
Sharon SethCommented:
It means that checked exceptions add more lines to your code , because you  use try , catch and finally blocks . You don't have to do this with unchecked exceptions.
Not sure where you picked those lines from , but I think it is in no way suggesting replacement of checked exceptions with unchecked exceptions . If your context requires a checked exception , you HAVE TO go for it.
0
 
gudii9Author Commented:
what is relation between unchecked exceptions and closures. please advise
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Sharon SethCommented:
Closures is a concept where you can pass some data and a block of code(closure) to a function (library), and the library will execute your closure on the data passed . When you do this , your block of code may throw some checked exceptions and the library has to somehow know how to handle/or pass on all these checked exceptions . This is called Exception Transparency
In general ,  checked exceptions are   not preferred by many as you have to write code to handle them even though they might not be thrown
0
 
gudii9Author Commented:
It means that checked exceptions add more lines to your code , because you  use try , catch and finally blocks . You don't have to do this with unchecked exceptions.

checked exceptions are   not preferred by many as you have to write code to handle them even though they might not be thrown

Unchecked exceptions do not need lot of code?
Please advise
0
 
gudii9Author Commented:
Common scenarios of Exception Handling where exceptions may occur
There are given some scenarios where unchecked exceptions can occur. They are as follows:
1) Scenario where ArithmeticException occurs
If we divide any number by zero, there occurs an ArithmeticException.

    int a=50/0;//ArithmeticException  

2) Scenario where NullPointerException occurs
If we have null value in any variable, performing any operation by the variable occurs an NullPointerException.

    String s=null;  
    System.out.println(s.length());//NullPointerException  

3) Scenario where NumberFormatException occurs
The wrong formatting of any value, may occur NumberFormatException. Suppose I have a string variable that have characters, converting this variable into digit will occur NumberFormatException.

    String s="abc";  
    int i=Integer.parseInt(s);//NumberFormatException  

4) Scenario where ArrayIndexOutOfBoundsException occurs
If you are inserting any value in the wrong index, it would result ArrayIndexOutOfBoundsException as shown below:

    int a[]=new int[5];  
    a[10]=50; //ArrayIndexOutOfBoundsException


http://www.javatpoint.com/exception-handling-and-checked-and-unchecked-exception

Above unchecked exceptions also needs  more lines to code , because we  use try , catch and finally blocks?
please advise
0
 
gudii9Author Commented:
how is handling exception and 'thrown so that application stops' are different. please advise
0
 
Sharon SethCommented:
Handling exception , most of the times is where you know that there is an exception , do whatever needs to be done in this situation , and go take the next course of action. The next course of action may be continuing with the execution of the rest of the program (that's what I meant when I said handle an exception) , or  very rarely halt and then throw , so that the execution stops.
What all I meant to say is , never handle/gobble up a runtime exception since a runtime exception clearly indicates an error
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.