Hi!
I'm using EOGenerator to generate my classes from the model.
Today, I found out that EOGenerator generates accessors using the
trusted key/value operations, like:
public String address() {
return (String)storedValueForKey(address);
}
public void
Hi!
Ok, tried takeValueForKey on setAddress and obviously got a stack
overflow (takeValueForKey actually calls setAddress!).
Is there any decent way to make a setter that DOES validation (ie,
without having to do takeStoredValueForKey( validateXPTO(value),
XPTO )?
Yours
Miguel
Am 22.08.2006 um 22:04 schrieb Chuck Hill:
It is not supposed to. validateAddress is intended to be called
_before_ setAddress is called. Right, wrong, or weird, that is how
EOF is intended to work. Objects are permitted to be invalid and
validity is checked during saveChanges().
