| 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 |