Re: [Q] validation and "sticky invalid values"
Re: [Q] validation and "sticky invalid values"
- Subject: Re: [Q] validation and "sticky invalid values"
- From: email@hidden (Anjo Krank)
- Date: Thu, 26 Jun 2003 23:37:49 +0200
- Xx-reply-to: email@hidden
Am Donnerstag, 26.06.03 um 22:21 Uhr schrieb Andrew Lindesay:
Hello;
A company I'm working with really wants to have the fields in a
component stick around in the case that a validation error occurs.
So, for example, some user enters some invalid values into a form that
is tied to an EO. Next they submit the values and those fields are
correctly validated as being broken. The EO does not actually take up
the values (as expected) and hence the unmodified values appear in the
response's outputted form again. Is there a "right" way to get those
values to get inserted into the EO regardless of their validity or
should I find some way to intercept the KVC mechanism at the component
level to achieve this? Of course I still need the validation
mechanism to run normally to avoid the EC from attempting to persist
invalid EO's.
Project Wonder has this functionality. IIRC, then you only override
validationFailedWithException() in your component to call eo.setFoo()
(which may or may not be a good idea depending on your datatype)
Cheers, Anjo
_______________________________________________
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.