• 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
WebServices question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WebServices question


  • Subject: WebServices question
  • From: Ramsey Gurley <email@hidden>
  • Date: Wed, 4 Mar 2009 16:55:15 -0500

Hi all,

I'm attempting to make use of WebObjects WebServices for the first time and I'm having some difficulty dealing with deserialized EOs. In my simple test setup, I have a server app and a client app with separate databases. I need to share information about entities between them. I've noticed that if I retrieve an EO from the server via SOAP, and then call eo.editingContext().saveChanges() on the client, the server data overwrites the data in the client database. In this case, the databases are separate but using the same EOModel. As a result, when saveChanges() is called the pk for server is totally unrelated to the pk on the client, and the data that is written to the db is completely unrelated to what was there before.

If I pass an EO, I currently know no way to differentiate between an EO that belongs to the client vs. the server. So I run the risk that one might get into an editing context that will be saved. Is there some trick to work around this or is this just the way the WO SOAP architecture is designed to work?

Thanks all,

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


  • Prev by Date: Re: Memory Management
  • Next by Date: Re: Memory Management
  • Previous by thread: Re: TOMCAT deployment + WebServerResources
  • Next by thread: display group madness...
  • Index(es):
    • Date
    • Thread