I kind of remember that the Deny delete rule worked as expected for
relationships that are not class properties. I just noticed that's no
longer the case, Deny is only acknowledged by validateForDelete() if
the relationship is marked as a class property.
Can anybody confirm this? Anybody else think this is somewhat of a
problem?
Looking at
/Developer/Examples/JavaWebObjects/Frameworks/JavaBusinessLogic/
Rentals.eomodeld
I see that, for example, the "videos" relationship on RentalTerms is
not class property and is using the Deny delete rule. Also, the
documentation on
http://developer.apple.com/documentation/WebObjects/UsingEOModeler/
5WorkingWithRelationships/chapter_5_section_5.html
doesn't mention anything about the class property requirement, nor do
the API docs for EORelationship, EOClassDescription, and EOCustomObject.
So the current examples and docs imply that Deny should work for non-
class properties. But as I said, it doesn't work (anymore).
Christian
_______________________________________________
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]
