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.
Let’s say you’ve got a Spring web app with a structure like this:
com/
myapp/
controller/
model/
service/
How should you handle exceptions that occur below the level of the controller?
Should you make methods in the Model and Service layers throw their exceptions up to the Controller layer?
What to do with them once they reach the Controller?
Do you always show the same error page to users but write a detailed exception to the log files?
It very much depends on the concrete case:
you can show the exception message (translated by some exception translation mechanism to a human-readable representation) together with validation message – for example “Email sending failed, please try again later”
If the exception can’t be recovered from, you can redirect to a page which will display human-readable explanation
you can redirect to a generic 500 page that says “Oops, something went wrong”
Pick one option that you feel best fits your use-case in terms of usability.