Thanks Henrique! That did the trick. Is the javadoc on willDelete just wrong about being called prior to validateForDelete? It would make sense for willDelete() to be called first, unless that is the sole intention of mightDelete(), in which case the willDelete() javadoc should be updated.
Dave On Aug 29, 2011, at 2:47 AM, Henrique Prange wrote: > Hi David, > > Have you tried the mightDelete method? It's called before the willDelete > method. > > Sent from my iPhone > > On 27/08/2011, at 22:40, David Avendasora <[email protected]> wrote: > >> Hi all, >> >> I have some business logic that I want to execute when an EO is deleted that >> reassigns some of the EO's related objects to another EO. I figured >> overriding willDelete() was the perfect place for it. >> >> The JavaDoc on willDelete states: >> >> "This method is also called before validateForDelete is called on this >> object." >> >> But in my D2W app when the ERMDDeleteButton is clicked, the >> validateForDelete is getting called first, before my implementation of >> willDelete, which would have taken care of the validation problem. >> >> Is using willDelete the wrong place to do this? If so, how do I get my >> business logic to execute when a ERMDDeleteButton button is clicked, but >> before validation is is called?! >> >> The implementation must be UI-independent. If anything tries to delete the >> EO (ERRest, D2JC, etc.) then this business logic should be executed. >> >> Dave >> _______________________________________________ >> 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/hprange%40gmail.com >> >> This email sent to [email protected]
_______________________________________________ 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]
