This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am currently building a sample we site using spring, but I have decided to post it here in Servlet since I think this is still servlet specific question.
Kindly look at my code. It just basically stream files into the response object so that the user can download it.
Now, my question is, how are we going to gracefully handle servlet exception?
Example is, I click the link to the file but the file isn't in the resources folder, my browser will just go blank as if nothing has happened.
But when I viewed my Tomcat logs, I saw that there is a Stream Closed Exception. I would like to know, how can I notify the user that there was an error
in downloading the file so that they are well informed instead of a blank browser screen.
I am not sure if this is possible...Thanks.
Sean Clark ---> I love this place!!!
Me ------> I definitely love this place!!!
mark reyes wrote:Now, my question is, how are we going to gracefully handle servlet exception?
Not by eating the exception as you are doing here.
If you want to handle exceptions in a global fashion, use the error page capability of the deployment descriptor. You should always set this up so that any unhanded exceptions have somewhere to go to handled in a reasonable fashion.
I am not sure if this is possible...
Of course it is. For specific exceptions that you don't want to go to the global handler, redirect to a page that explains the problem when you detect the exception.