On Apr 14, 2008, at 12:37 PM, Florijan Stamenkovic wrote:
Hi all,
I'm wondering how many people use (and depend on)
NSValidation.ValidationException aggregation capabilities,
especially in validateForDelete?
I use them, but not in validateForDelete. Or not often...
The thing being, I'm re-writing client side EO validateForDelete(),
and actually would prefer to switch to non-aggregated exceptions,
meaning, first deletion rule validation, an exception is thrown,
period. I know to some degree it is a poorer system, but I've
personally never used aggregated exceptions, and could live without
them...
Words of wisdom anyone?
I don't see that as a large problem for validateForDelete.
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
