Vijitha has already pointed out the error in the first part of the post.
Originally posted by Eric Daly:
So you don't necessarily need to use try/catch, although it is good practice to do so. I hope that helps.
It's generally
not good practise to try/catch for unchecked exceptions, as their arising is usually an indication of a bug in the code and/or a wrong runtime environment, missing resources and the like.
Only in exceptional cases (no pun) it may be desirable to trap a runtime exception and continue execution, with or without information to the user.