On Jun 21, 2010, at 2:10 PM, James Cicenia wrote:
> Hello -
>
> I am doing this:
>
> if(att1.alertTarget()==null || att1.percentageOfAlert() == null ){
>
> currentMasterAlert.removeFromAlertThresholdTargetsRelationship(att1);
> currentMasterAlert.ctEditingContext().deleteObject(att1);
> att1 = null;
> }
>
>
> but get this:
>
> [2010-6-21 16:4:50 CDT] <WorkerThread8> Validation failed on an object [null]
> with keypath = att3.alertTarget and exception: The alertTarget property of
> AlertThresholdTarget must have a AlertTarget assignedYou probably don't need the removeFromAlertThresholdTargetsRelationship, the model is probably doing that for you. > Yet it does delete the entity: Does it save the delete? > Why does it want to run validation during a delete? Validating Before an Operation The EOValidation methods -- validateForInsert, validateForUpdate, validateForSave, and validateForDelete -- validate an entire object to see if it's valid for a particular operation. These methods are invoked automatically by the Enterprise Objects Framework when the associated operation is initiated. http://developer.apple.com/legacy/mac/library/documentation/MacOSXServer/Reference/WO54_Reference/com/webobjects/eocontrol/EOValidation.html Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
