Rockford Lhotka's CSLA .NET uses a "Broken Rules" collection that represents
each of the validation failures for a domain object.
Unfortunately his site appears to be down temporarily...
Hope this helps
|I am building a stateless distributed web application which has validation
| of information performed in many layers. Most of the validation will be
| repeated in both the UI and business layers as the code is structured to
| also expose functionality as a web service. More advanced validation will
| done in both the business layer and data layer e.g. validating groups of
| related properties or related information in rows of data
| When validating the information for 'anticipated' problems (errors and
| warnings), I want to collect all of the various errors/warnings and report
| them back to the UI as some sort of collection. Ideally, I would prefer
| to pass the collection between methods so was looking at possibly using a
| singleton but I would have to somehow isolate the collection per user's
| session since the app is 'mostly' stateless.
| I have searched the net and found many great articles on Exception
| Management but nothing detailed on validation. Can anyone recommend an
| approach or point me to some articles?