Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Most of the exceptions thrown in spring are runtime exceptions which tend not be highlighted by eclipse (for me anyway). Is it just a case of learning what can be thrown and when or is there a better way of doing this. The reason i ask is because i find myself missing the catching of the run time exceptions and this obviously is not good.
Thanks
Most runtime exceptions are things you can’t do anything about anyway, so your not catching them is mostly just as well. You should have an exception handler set up to catch all exceptions from the controller anyway, since you will want to log RuntimeExceptions regardless. There are some subclasses of DataAccessException (the one for handling violated unique constraints comes to mind) that you may need once in a while, but for the most part it shouldn’t be an issue in practice.
TLDR version: I’ve been using Spring since 2004 and I know hardly any of the unchecked exceptions thrown by Spring. Don’t worry about it, it’ll be ok.