Re: Best Practice? - error handling
Re: Best Practice? - error handling
- Subject: Re: Best Practice? - error handling
- From: Marek Wawrzyczny <email@hidden>
- Date: Thu, 12 Aug 2004 09:26:31 +1000
On 11/08/2004, at 04:29, Kieran Kelleher wrote:
Check out this approach .... I like it, works well.
http://www.stepwise.com/Articles/Technical/2001-06-13.01.html
-Kieran
I've extended on the idea detailed in the article a little further. All
my components subclass my own component class that captures and stores
the validation exceptions in an array. I then make this array available
to the component.
I also have two other sub-components ValidationMessage and
ValidationContainer that take the validation exception array, a key,
and an EO object as its bindings. These components then search the
validation exception arrays for any corresponding messages (if any). So
all my property entry fields on the page now have a corresponding
validation message, even if at present I am not validating that
property.
I also have mechanism for adding custom ValidationExceptions.
All of this happens fairly automatically.
Marek Wawrzyczny
software engineer
-------------------------->
ish group pty ltd
http://www.ish.com.au
7 Darghan St Glebe 2037 Australia
phone +61 2 9660 1400 fax +61 2 9660 7400
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.