Mailing-List: contact cayenne-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cayenne-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <f65b8ae30611271030r9aa1c2fm437c8c94ef2cda29@mail.gmail.com>
References: <456B20E1.1080602@maine.rr.com>
 <f65b8ae30611271030r9aa1c2fm437c8c94ef2cda29@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3FD24A9D-E17F-455B-B77E-46FD3B63CEF6@centralparksoftware.com>
Content-Transfer-Encoding: 7bit
From: Matt Kerr <matt@centralparksoftware.com>
Subject: Re: can't modify relationships in validateForUpdate()?
Date: Mon, 27 Nov 2006 14:11:55 -0500
To: cayenne-user@incubator.apache.org

trying to recall ..   so, i would double check this, but --

> Perhaps this is because of my WO/EOF background, but I had always
> assumed that modifying anything in the validate* methods would be a
> Bad Thing and never tried doing it.

is this because WO/EOF specifically guides you *not* to put any side- 
effect code into the validate* methods.

but i want to say this was ok .. since there were other delegate  
methods to tidy up before validateFor* was invoked ..

(now - if i could just remember which one .. hmm.  is that right?)


> I can't say I ever read it in regards to Cayenne, but it feels like  
> the right thing to me.
> Not sure why it changed in behavior, though.


in cayenne -- there is no equivalent delegate .. and i believe the  
right/best way to handle this situation is to implement the side- 
effects in validateFor*().


-mk