• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Another JavaClient bug???
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another JavaClient bug???


  • Subject: Re: Another JavaClient bug???
  • From: Ken Anderson <email@hidden>
  • Date: Sun, 28 May 2006 15:39:58 -0400

Flor,

The behavior you're illustrating is possible under certain circumstances with server-side EOF. The important questions are, how is the relationship setup, and how are you deleting the object? Also, when are you calling the books relationship to test? After save?

I'm not sure, but my guess is, if you don't have a relationship from books back to author with a nullify delete rule, the object will continue to exist in the books() relationship in author.

Ken



On May 28, 2006, at 9:19 AM, Florijan Stamenkovic wrote:

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:
40anderhome.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
  • Follow-Ups:
    • Re: Another JavaClient bug???
      • From: Florijan Stamenkovic <email@hidden>
References: 
 >Another JavaClient bug??? (From: Florijan Stamenkovic <email@hidden>)

  • Prev by Date: Re: generating response in different thread
  • Next by Date: Re: Another JavaClient bug???
  • Previous by thread: Another JavaClient bug???
  • Next by thread: Re: Another JavaClient bug???
  • Index(es):
    • Date
    • Thread