It does seems that GWT RPC does perserve object graphs properly. I use
Twig to persist to the DataStore and that is were my object graph gets
messed up. So, new investigations...
Juan, Paul, thanks for your inputs, they led me in the right
direction.
Carl
On Mar 24, 3:15 pm, Paul Robinson wrote:
GWT RPC does normally preserve object graphs properly, so an instance is only
ever written out once. If the same object is referenced multiple times in an
object graph, the first time it writes out the full object, and subsequent
times it writes a reference back to the thing it wrote out before
GWT-RPC serialize objets graphs by POST and isn't do exact JVM
serialization. You must implement equals and hashcode and then if you
compare with equals then:
Before serialization: instance x of A.bs equals instance x of C.bs.
After deserialization: instance x of A.bs equals instance x of C.bs.
2
Hi,
I have the following setup:
import java.io.Serializable;
class A implements Serializable {
Set bs;
Set cs;
}
class B implements Serializable {
Set cs;
}
class C implements Serializable {
Set bs;
}
I send an instance of A from client to server using GWT RPC. A
