Home/ Questions/Q 7566281
In Process

The Archive Base Latest Questions

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

I have a class XYZ whose public functions throw Exception s. I have been

  • 0

I have a class XYZ whose public functions throw Exceptions.

I have been advised that all public functions exposed by XYZ should throw exceptions called XYZDataException or XYZSystemException. So even if I get other exceptions within the public methods they need to be wrapped by these XYZExceptions.

I have a couple of questions:

  1. What is the advantage of wrapping exceptions with XYZException?
  2. What is the advantage of differentiating between System and Data exceptions?

To me it feels right to just throw whatever exception occurs without wrapping it further.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A lot of Exception handling depends on how you plan on extending it later on. For example, if developer B came along and wanted to modify some of your code, it would be a lot easier if he understand what Exception meant what in which case. In that case, having specific Exceptions makes more sense.

    As to breaking up System and Data exceptions – a Data exception would basically be something that should be non-fatal that occurs because of bad data. A System exception would be because your System failed in some way. Again, this all points to how you want to use it later on. If you want to use your code solely, and you don’t care about how your exceptions come back out, then by all means, go with what is easiest at the time.

    I have found that when working with other developers on a project, it is a lot easier for them to grasp what is going on when you subclass your Exceptions and throw them in specific cases.

    Hope this helps!

    • 0