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.
I have been in both situations:
In both cases the project started OK but soon became an overhead to maintain (and refactor).
So what is the best practice regarding the creation of your own Exception classes?
The Java Specialists wrote a post about Exceptions in Java, and in it they list a few ‘best practices’ for creating Exceptions, summarized below:
Don’t Write Own Exceptions (there are lots of useful Exceptions that are already part of the Java API)
Write Useful Exceptions (if you have to write your own Exceptions, make sure they provide useful information about the problem that occurred)