Exceptions: What to handle, what to throw [closed]
Closed 8 years ago.
Exceptions: What to handle, what to throw [closed]
Closed 8 years ago.
Exceptions: What to handle, what to throw [closed]
Closed 8 years ago.
Exceptions: What to handle, what to throw [closed]
Closed 8 years ago.
Should service layer catch all dao exceptions and wrap them as service exceptions?
I have three layer Spring web app: dao, service and controllers. A controller never calls directly the dao, it does it through the service layer. Right now, most of the time if there is dao exception (runtime) that is not handled, it’ll be caught by a JSP showing an error message to the end user.
Should service layer catch all dao exceptions and wrap them as service exceptions?
Java exception handling design
I am trying to design a simple exception handling strategy for web services middleware using some ideas from here: http://northconcepts.com/blog/2013/01/18/6-tips-to-improve-your-exception-handling/.
Java exception handling design
I am trying to design a simple exception handling strategy for web services middleware using some ideas from here: http://northconcepts.com/blog/2013/01/18/6-tips-to-improve-your-exception-handling/.
Advice needed on rethrowing an exception
Consider the following c# code:
Under which circumstances does it make sense to lose track of where an exception was thrown from?
Is there any valid reason why a catch block on a lower layer would throw back an exception caused by a higher, unknown layer using the following syntax:
How should I handle logger failures?
In several of our company’s applications, we use a custom logger. It’s fairly robust, though we may replace it with something like NLog in the future. One of the logger’s tasks is to log any exceptions encountered in the application.