KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I do not understand the advantages of having a chained exception in the code. Considering the ResourceLoader example from java world , if the programmer knows of a possibility of encountering ResourceLoadException , why not catch the same exception instead of SQLException ? Else, the programmer can catch both the exceptions in the same code than having to throw a new Throwable instance?
Tags (comma-separated)
Save Edits
Cancel