>>> Because then the user loses what they typed which can sometimes be annoying
>>> (e.g., if it's too long a string etc)
>>
>> As i said: then push the invalid value. This is what ERXValidation does.
>
> And if the value's of the wrong type or can't be coerced?
if (eo instanceof EOEnterpriseObject) {
// the exception is coming from EREnterpriseObject
// WE PUSH THE WRONG VALUE INTO THE EO ANYWAY!
if (pushChanges) {
try {
((EOEnterpriseObject)eo).takeValueForKeyPath(value,
key);
} catch(NSKeyValueCoding.UnknownKeyException ex) {
// AK: as we could have custom components that have
non-existant keys
// we of course can't push a value, so we discard the
resulting exception
} catch(Exception ex) {
log.error("Can't push value to key '" + key + "': " +
value, ex);
}
}
Cheers, Anjo
_______________________________________________
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]
