Monday, August 22, 2005

Part 2 - Error Handling (Not Exceptions)

Discussions have lead to a couple of resolutions to the problem at hand.

  1. Creating an event on the necessary object that gets raised whenever an error occurs.
  2. Creating an errorMessage field/property that's normally null, but gets set any time an error occurs. It's up to the developer to check the field before using the object.
  3. Similar to 2, except you create an Error object that has properties and such that get set on error.
  4. Similar to 2 also, create an Enumeration, along the lines of ObjectStatus, that all Business Objects have to indicate the state of the object at all times.

Any other suggestions out there?


No comments: