In response to incorrect data, the API will throw a
number of Excepion.They may be caused by the following
types.
1. Incorrect data such as input less than < min
2. Business rule violation
3. Database errors
4. Any other exception in any layer
5. Unexpected run time errors due to network problem,
db down , problems db schema objects and so on.
Some of these exceptions needs to be handled in
special ways to inform the user exactly how he can
resolve it. Data errors and business rules belong in
this category. The user can correct his input and work.
Other errors and run time exceptions such as a db down
also needs to be shown to the user to some degree of
information, such as an advice to contact his admin
since db is down.
Unexpected errors also needs to be shown to the user
but exact details may not be useful to a user.
A chassis ui error handler needs to be developed with
capability to handle these situations including
unexpected errors.
Exceptions that may happen in the UI also needs to be
handled this way.