Home/ Questions/Q 6109151
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T14:22:23+00:00

I understand throwing exceptions specific to the application layer you’re in, but what is

  • 0

I understand throwing exceptions specific to the application layer you’re in, but what is the purpose of all of this exception handling overhead if you’re:

  1. Just going to let the exceptions bubble up to the top.
  2. Never going to do anything “unique” with the wrapped exception.

For example, I have a DAO that throws a SQLException, and the next layer up is a manager that calls the DAO. The commonly accepted paradigm is that I create a manager exception, wrap my SQLException, and then throw the manager exception. Why? If another class up the chain is going to deal with it anyhow, then why wrap it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In your example, it might not be useful. But suppose you’re writing an interface with many possible implementations. Suppose for example that two years from now, you switch from a SQL database to a NoSQL one. Your DAO will then be forced to declare NoSQLException, and all the calling code will have to be rewritten. Whereas if the SQLException or NoSQLException is wrapped inside your custom exception, the calling code can stay as it is.

    • 0