Related objects will only be serialized if they have been resolved.
Otherwise they will still be Faults after deserialization.
On client-side objects will not be automatically attached to the context,
because readObject() and writeObject() methods are not defined in
client-CDO's
2009/3/29 Andrus Adamchik <andru..bjectstyle.org>
> I should add that on the server side, the usual serialization pattern was
> to serialize the entire context. This way there's no need to think which
> part of the object graph needs to be serialized, and on de-serialization
> objects are automatically attached to the context.
>
> Haven't tried it on the client.
>
> Andrus
>
> On Mar 29, 2009, at 10:34 AM, Andrey Razumovsky wrote:
>
> Why not? ROP objects are obviously serializable, and their "objectContext"
>> field is transient, so no problems should occur. You should only watch
>> that
>> all objects have correct persistenceState (e.g. they are not COMMITED
>> without being registered to objectContext)
>>
>> 2009/3/27 Zissis Trabaris <z.trabari..nsysware.com>
>>
>> The question at hand is: Given an ROP client object retrieved from the
>>> database, can I serialize it to disk, later on, de-serialize it to
>>> memory, register it to a context and use it as if it came from the
>>> database? Some caveats of course... Assume the database did not change
>>> since the serialization process took place.
>>>
>>>
>>>
>>> Zissis Trabaris * Chief Technology Officer * INSYSWARE * 3235 West River
>>> Road, Grand Island, New York, 14072, USA
>>> Mobile (716) 930-5654 * Office (518) 636-4118 * Fax (716) 625-1305 *
>>> z.trabari..nsysware.com <mailto:%20%20z.trabaris@insysware.com<20%2520z.trabaris@insysware.com>
>>> <20%2520z.trabari..nsysware.com <20%252520z.trabaris@insysware.com>>>
>>> *
>>> www.insysware.com <http://www.insysware.com/>
>>>
>>>
This archive was generated by hypermail 2.0.0 : Sun Mar 29 2009 - 04:18:57 EDT