Re: Owns Destination problem
Re: Owns Destination problem
- Subject: Re: Owns Destination problem
- From: Florijan Stamenkovic <email@hidden>
- Date: Tue, 19 Aug 2008 13:36:42 -0400
Hi Dave,
Note these lines in the stack:
at com.webobjects.eocontrol.EOCustomObject.validateForSave
(EOCustomObject.java:1411)
at com.webobjects.eocontrol.EOCustomObject.validateForInsert
(EOCustomObject.java:1473)
What exactly are you doing in your app? It looks as though your EOs
are being treated as newly inserted EOs, instead of having deletion
rules processed.
Also, a bit weird, I don't see a call to #processRecentChanges() in
the stack. I thought that should always happen before any validation,
to prepare the object graph for it...
Well, maybe it makes more sense to someone with more knowledge of
EOF's ins and outs.
HTH
F
On Aug 19, 2008, at 10:37, David Avendasora wrote:
Hi all,
This is very confusing, and I know it should be a very simple
thing. I have a the following relationship that is marked as Owns
Destination,
ManufacturingSchedule <->> ScheduledRouting
When I remove the ScheduledRouting from the ManufacturingSchedule's
scheduledRoutings() relationship by calling
removeObjectFromBothSidesOfRelationshipWithKey
(scheduledRoutingToDelete, "scheduledRoutings");
on the ManufacturingSchedule, the ScheduledRouting is not being
deleted when I call editingContext().saveChanges(). Instead I'm
getting a validation error:
[2008-08-19 09:44:57 EDT] <WorkerThread0>
<com.webobjects.appserver._private.WOComponentRequestHandler>:
Exception occurred while handling request:
com.webobjects.foundation.NSValidation$ValidationException: The
manufacturingSchedule property of ScheduledRouting must have a
ManufacturingSchedule assigned
[2008-08-19 09:44:57 EDT] <WorkerThread0>
com.webobjects.foundation.NSValidation$ValidationException: The
manufacturingSchedule property of ScheduledRouting must have a
ManufacturingSchedule assigned
at com.webobjects.eoaccess.EORelationship.validateValue
(EORelationship.java:1805)
at
com.webobjects.eoaccess.EOEntityClassDescription.validateValueForKey
(EOEntityClassDescription.java:443)
at com.webobjects.eocontrol.EOCustomObject.validateValueForKey
(EOCustomObject.java:1339)
at com.webobjects.eocontrol.EOCustomObject.validateForSave
(EOCustomObject.java:1411)
at com.webobjects.eocontrol.EOCustomObject.validateForInsert
(EOCustomObject.java:1473)
at com.webobjects.eocontrol.EOEditingContext.validateTable
(EOEditingContext.java:2249)
at com.webobjects.eocontrol.EOEditingContext.validateChangesForSave
(EOEditingContext.java:3029)
at com.webobjects.eocontrol.EOEditingContext._prepareForPushChanges
(EOEditingContext.java:3283)
at com.webobjects.eocontrol.EOEditingContext.saveChanges
(EOEditingContext.java:3213)
Why isn't it just deleting the ScheduledRouting object on save? All
of ScheduledRouting's relationships are either Cascade or Nullify,
so I know that it isn't being held onto because of a delete rule.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
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