They differ if the try-block completes by throwing a java.lang.Throwable that is not a java.lang.Exception, for instance because it is a java.lang.Error such as AssertionError or OutOfMemoryError. the try-block completes abruptly using a control flow statement such a continue, break or return the catch-block completes abruptly (by throwing any throwable, or using a control flow … Read more
There are a number of inaccuracies in the other answers. Control is passed to the finally block when control leaves the try block normally — that is, by a return, goto, break, continue, or simply falling off the end. Control is passed to the finally block when control leaves the try block via an exception … Read more
Yes, the finally block gets run whether there is an exception or not. Try [ tryStatements ] [ Exit Try ] [ Catch [ exception [ As type ] ] [ When expression ] [ catchStatements ] [ Exit Try ] ] [ Catch … ] [ Finally [ finallyStatements ] ] –RUN ALWAYS End … Read more
Returning from inside a finally block will cause exceptions to be lost. A return statement inside a finally block will cause any exception that might be thrown in the try or catch block to be discarded. According to the Java Language Specification: If execution of the try block completes abruptly for any other reason R, … Read more
It does not give a compilation error because it is allowed by the Java Language Specification. However, it gives a warning message because including a return statement in the finally block is usually a bad idea. What happens in your example is the following. The return statement in the try block is executed. However, the … Read more
Yes, it is different. Finally will always run (barring program crash). If the function exits inside of the try catch block, or another error is thrown in either the try or the catch, the finally will still execute. You won’t get that functionality not using the finally statement.
The proper way to do it is probably to break down the method by putting the try-catch block in a separate method, and use a return statement: public void someMethod() { try { … if (condition) return; … } catch (SomeException e) { … } } If the code involves lots of local variables, you … Read more
It is overridden by the one in finally, because finally is executed after everything else. That’s why, a rule of thumb – never return from finally. Eclipse, for example, shows a warnings for that snippet: “finally block does not complete normally”
remove return statement from it. Final block is considered to be cleanup block, return is not generally expected in it.
Because if an exception gets thrown no code after the try block is executed unless the exception is caught. A finally block is always executed no matter what happens inside your try block.