What is the advantage of chained exceptions

by

Can anyone please provide information on the need for chained exceptions?

The article says it quite well:

Exception chaining allows you to map one exception type to another, so that a method can throw exceptions defined at the same abstraction level as the method itself, without discarding important debugging information.

That is, if you have a method that loads some object from a database, you may rather want some ResourceLoadException (closer related to the methods abstraction level) instead of a low-level SQLException even if that was the original source of the problem. However, if you simply catch the SQLException and throw a ResourceLoadException instead, you may loose important debugging information.

Thus, chaining the exceptions is a good alternative. You throw a “high-level” exception, well suited for the particular method, but chain it with the exception that caused it.

Else, the programmer can catch both the exceptions in the same code than having to throw a new Throwable instance?

I don’t quite follow your reasoning here. The point is that he should not need to worry about the SQLException at this level of abstraction.

More Related Contents:

  1. Analyze the following code, which exception does it display? (Exception handling, java)
  2. is it good practice to call a method from Exception block in java?
  3. Can’t get ArrayIndexOutOfBoundsException from Future and SwingWorker if thread starts Executor
  4. Handling InterruptedException in Java
  5. Is it a bad practice to catch Throwable?
  6. Java 8: Lambda-Streams, Filter by Method with Exception
  7. Good way to encapsulate Integer.parseInt()
  8. Spring Boot REST service exception handling
  9. Java unreported exception
  10. Increasing heap space in Eclipse: (java.lang.OutOfMemoryError)
  11. Exception handling : throw, throws and Throwable
  12. How do I fix a compilation error for unhandled exception on call to Thread.sleep()?
  13. try with resources introduce unreachable bytecode
  14. How to loop user input until an integer is inputted?
  15. Java: Global Exception Handler
  16. Differences between Runtime/Checked/Unchecked/Error/Exception
  17. Java if vs. try/catch overhead
  18. Throws or try-catch
  19. Mockito How to mock and assert a thrown exception?
  20. Why can I throw null in Java? [duplicate]
  21. Java uncaught global exception handler
  22. Why does order matter when catching exceptions?
  23. Why is “throws Exception” necessary when calling a function?
  24. Guidelines on Exception propagation (in Java)
  25. Who is calling the Java Thread interrupt() method if I’m not?
  26. Why do Java people frequently consume exceptions silently?
  27. In Java how can I validate a thrown exception with JUnit?
  28. Why am I getting “must be caught or declared to be thrown” on my program?
  29. CompletableFuture already completed with an exception
  30. Is it okay to throw NullPointerException programmatically? [closed]

Leave a Comment