Re: Cannot obtain globalId for an object which...
Re: Cannot obtain globalId for an object which...
- Subject: Re: Cannot obtain globalId for an object which...
- From: Ricardo Parada <email@hidden>
- Date: Tue, 20 Sep 2016 18:19:15 -0400
Hi Chuck,
I followed the steps of the code and I noticed that the object containing the to-many relationship in question is being local instanced in a peer editing context. The to-many is still an array fault which has not been triggered.
Then when the object in the original context has its to-many triggered, i.e. by calling:
analysis.groupings().count();
Where analysis is the EO and groupings() is the to-many then the exception is generated.
It appears to have that if I trigger the to-many early on then the exception is avoided.
Anyways, I will experiment a little bit more with the problem and report back. I don't recall seeing something like this before and I local instance objects from one editing context to another all the time.
Thanks
On Sep 20, 2016, at 5:21 PM, Chuck Hill < email@hidden> wrote:
A full stack track would help. It sounds like your code is making a relationship between objects in different editing contexts. Did someone forget to add a “localInstance”?
All of a sudden one of our apps started getting this. Does anybody know why this would happen? It did not seem to have a problem before until now.
Cannot obtain globalId for an object which is registered in an other than the databaseContext's active editingContext,
object: <UBAnalysis pk:"84106">,
databaseContext: com.webobjects.eoaccess.EODatabaseContext@3935ae60,
object's editingContext: er.extensions.eof.ERXEC@4247ac26,
databaseContext's active editingContext: er.extensions.eof.ERXEC@c0fc23d’
|
_______________________________________________
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