Hi,

On Mar 19, 2006, at 11:13 AM, Florijan Stamenkovic wrote:


It appears that validateForDelete() does not check against the model for deletion rules in three tier java clients. It appears it does just about nothing. Which is surprising as validateForSave() and attribute validation, for example, work perfectly. I am about to dive deeper into the problem, and was wondering if anybody has any experience there already?

As always, when it comes to three tier problems, both the documentation and list resources are damn scarce... No results when searching there.

I can't find the e-mail that I thought I had, but I have found a couple of things with class descriptions that did not work correctly client-side. I think that delete rules were one of them. Certainly worth a report at bugreport.apple.com

Chuck


--
Coming in 2006 - an introduction to web applications using WebObjects and Xcode http://www.global-village.net/wointro

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




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

Reply via email to