Another JavaClient bug???
Another JavaClient bug???
- Subject: Another JavaClient bug???
- From: Florijan Stamenkovic <email@hidden>
- Date: Sun, 28 May 2006 15:19:49 +0200
Hi all,
I am working on a Java Client WO application. I realized something
weird is happening in the client side EOF, and I need confirmation
that it is NOT the standard behavior of server side frameworks.
If I have a Book object that is related to an Author object ( Author
<--->> Book ), and I delete the Book object in the editing context
where both of them are registered (the only one in the application
btw), I still get that specific Book object among others in the
resolving of the Author.books() relationship. It seems to be that the
editing context does NOT unrelate objects according to delete rules
on deletion. I have not worked much with server side frameworks for a
while now, but as far as I remember, this is NOT how it is happening
on that side, right???
This would not be surprising, as already there is a confirmed bug in
client side frameworks, where delete rules are not at all considered
in object validation (validateForDelete()). It seems that the class
descriptions that are transferred to the client side are faulty in
that sense.
Please, anybody who can confirm this, report it also at
http://bugreport.apple.com/
Best regards,
Flor
_______________________________________________
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