EOGenerator and takeStoredValueForKey dumb question
EOGenerator and takeStoredValueForKey dumb question
- Subject: EOGenerator and takeStoredValueForKey dumb question
- From: Miguel Arroz <email@hidden>
- Date: Tue, 22 Aug 2006 19:00:00 +0100
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 setAddress(String aValue) {
takeStoredValueForKey(aValue, "address");
}
This causes that, when I use setAddress(address), the value does
not go trough the validateAddress method.
This looks strange, but I suppose there are any reasons why
EOGenerator authors prefered the trusted operators instead of the
normal "takeValueForKey" ones. Anyone knows why? Is there a problem
if I change the templates to use the normal operators?
Yours
Miguel Arroz
"The world lies in the hands of evil
And we pray it would last" -- Apocalyptica, Life Burns!
Miguel Arroz
http://www.ipragma.com
_______________________________________________
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