| Hi John,
Could be you did it in “validateForSave()” You shouldn’t be changing values there, only throwing validation errors.
Grab the snake by its tail, start pulling, keep doing it until you find the head.
Namely, put your break point not in your “validateRelationship” method but more directly in your “updateRelationship” method which should be in your abstract “under bar” class for the EO. That is much closer to the scene of the crime. Try that and report back.
Oh, notice how the “validateRelationship” and “validateAttribute” methods always return an object? That is the potentially coerced object that EOF will use to update the EO. In contrast, “validateForSave()” is a void… That is a subtle clue to never do object manipulation in “validateForSave()”
Of course I’m stabbing in the dark here but “grabbing the tail of the snake” will make whatever it is clear.
May the 4th be with you.
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
|