No, you generally don't need to put return values in finally blocks. Finally blocks are usually used for resources that need to be released, such as closing files or database connections. Your method could easily be rewritten as:
If its a simple what you said would be fine . But if i am dealing with any Data Base connections then i should be dealing with the try and catch blocks in that case i am asking.
One of the reasons/purposes of having a try/catch/finally block is to separate out error handling from the normal flow of your code. the normal operation goes in the 'try', the error goes in the 'catch', and the 'i really need to clean up' goes in the 'finally'.
Since the return is part of the normal flow, it could go in either the 'try' or outside of the try/catch block all together. some folks argue that the ONLY think that should go in the try is stuff that can throw the exception, and your return statement is not one of them.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
Whatever you place in Finally will run regardless of what happens as a result of your try/catch block so only put code in the finally block that you always want to run.
No holds barred. And no bars holed. Except this tiny ad:
a bit of art, as a gift, the permaculture playing cards