Re: Running validation manually
Re: Running validation manually
- Subject: Re: Running validation manually
- From: Mark Wardle <email@hidden>
- Date: Thu, 7 Jan 2010 10:51:59 +0000
Hi Miguel,
Thank you. I re-implemented this and it now works. I suspect I had one
of my own validateXXX() methods in one entity subclass that was doing
something stupid.
I thought there would be considerable overhead in running
validateForSave() but timing this suggests it is quite efficient.
I would otherwise cache the result but then wouldn't know when an EOF
was changed (ie. a property was changed but not necessarily saved).
Thanks,
Mark
2010/1/7 Miguel Arroz <email@hidden>:
> Hi!
>
> On 2010/01/07, at 00:04, Mark Wardle wrote:
>
>> Unfortunately this naive solution does not work as it appears my
>> application locks in validateForSave(). No warnings or errors.
>
> That's very weird. Even if you entered an infinite loop, it should
> eventually explode with a stack overflow. Try to use the debugger to see
> what's happening, you may be stuck with a simple implementation bug
> somewhere in the validation code.
>
> Yours
>
> Miguel Arroz
--
Dr. Mark Wardle
Specialist registrar, Neurology
Cardiff, UK
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden