Re: JC client side EO encoding problem
Re: JC client side EO encoding problem
- Subject: Re: JC client side EO encoding problem
- From: Stamenkovic Florijan <email@hidden>
- Date: Fri, 24 Apr 2009 11:48:41 -0400
Hi guys,
Thanks for your replies...
I believe I've found the culprit. I wasn't releasing my "to-delete"
cache after saving, which resulted in something like
ec.deleteObject(someEO); // someEO is a valid object for deletion at
this point
ec.saveChanges();
ec.deleteObject(someEO); // obviously this is idiotic
ec.saveChanges();
I've fixed it, so that should be it. In the remote case this was
caused by something else, I will get back on it.
Thx,
F
On Apr 24, 2009, at 11:09, David Avendasora wrote:
Hey Flor,
What follows is entirely speculation. It makes sense to me, but I
don't know how grounded in reality it is. With that said...
I've seen this when the client-side and server-side classes were not
able to be serialized into each other (does that make any sense?)
I had the problem when I tried to add an Inner Class to the server-
side class, but the client didn't have the Inner Class. I _think_
the structure of the class on the client and server have to be the
same otherwise they can't be serialized and passed back and forth as
though they are the same class. Normally the EOModel defines both
classes so they are close enough.
Are the client- and server-side classes substantially different?
Dave
On Apr 24, 2009, at 11:02 AM, Stamenkovic Florijan wrote:
Has anyone seen anything like this before:
[Apr 23, 2009 21:03:31 -0400] Exception thrown:
java.lang.IllegalArgumentException: encodeObject: unable to encode
object of class com.havaso.dvis.client.eof.eo.UserGroup
at
com
.webobjects
.eodistribution
.common
._EOReferenceRecordingCoder
.encodeObject(_EOReferenceRecordingCoder.java:348)
at
com
.webobjects
.eodistribution
.common
._EOReferenceRecordingCoder
.encodeObjects(_EOReferenceRecordingCoder.java:375)
at com.webobjects.foundation.NSArray.encodeWithCoder(NSArray.java:
1330)
at
com
.webobjects
.eodistribution
.common
._EOReferenceRecordingCoder
.encodeObject(_EOReferenceRecordingCoder.java:344)
at
com
.webobjects
.eodistribution
.common
._EOReferenceRecordingCoder
.encodeObjects(_EOReferenceRecordingCoder.java:375)
at
com
.webobjects
.eodistribution
.common
._EOServerInvocation.encodeWithCoder(_EOServerInvocation.java:79)
at
com
.webobjects
.eodistribution
.common
._EOReferenceRecordingCoder
.encodeObject(_EOReferenceRecordingCoder.java:344)
at
com
.webobjects
.eodistribution
.common
._EOReferenceRecordingCoder
.encodeObjects(_EOReferenceRecordingCoder.java:375)
at com.webobjects.foundation.NSArray.encodeWithCoder(NSArray.java:
1330)
at
com
.webobjects
.eodistribution
.common
._EOReferenceRecordingCoder
.encodeObject(_EOReferenceRecordingCoder.java:344)
at
com
.webobjects
.eodistribution
.client.EOHTTPChannel._responseToMessage(EOHTTPChannel.java:542)
at
com
.webobjects
.eodistribution
.client.EOHTTPChannel.responseToMessage(EOHTTPChannel.java:640)
at
com
.webobjects
.eodistribution
.client
.EODistributedObjectStore._send(EODistributedObjectStore.java:651)
at
com
.webobjects
.eodistribution
.client
.EODistributedObjectStore
.saveChangesInEditingContext(EODistributedObjectStore.java:475)
at
com
.webobjects
.eocontrol.EOEditingContext.saveChanges(EOEditingContext.java:3192)
...
Where UserGroup is a standard issue EO. Note that this is entirely
arbitrary, I can for example save, update or delete any number of
UserGroup records, or other records for that matter, and not see
this. Then out of nowhere, this happens.
Any thoughts?
Thx,
F
_______________________________________________
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
_______________________________________________
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