[sending to devel]
> I thought about proposing that, but won't it conflict with the
> scenarios where DataContext does get serialized?
Not unless deserialized context is also bound to the current thread.
Before making a final decision, I guess it is worth testing this in a
servlet environment with clustering and Cayenne request filter.
> Also, (and this shows my serialization ignorance), won't providing a
> readResolve method force you to return other than the serialized
> object? Is it legal to return "this"?
AFAIK it should be ok to return "this".
Andrus
Begin forwarded message:
> From: Mike Kienenberger <mkienen..mail.com>
> Date: September 27, 2005 3:25:56 PM EDT
> To: cayenne-use..bjectstyle.org
> Subject: Re: Reconnecting serialized DataObjects
> Reply-To: cayenne-use..bjectstyle.org
>
>
> I thought about proposing that, but won't it conflict with the
> scenarios where DataContext does get serialized?
>
> Also, (and this shows my serialization ignorance), won't providing a
> readResolve method force you to return other than the serialized
> object? Is it legal to return "this"?
>
> On 9/27/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
>
>>
>> On Sep 27, 2005, at 3:10 PM, Mike Kienenberger wrote:
>>
>>
>>> When I get it all figured out, I'll try to write up a wiki
>>> article on
>>> it since the question comes up every so often.
>>>
>>
>> In fact a working WedgeDataObject that handles serialization is worth
>> merging into CayenneDataObject (with a try/catch around block that
>> retrieves thread DataContext to fail over to the default behavior).
>>
>> Andrus
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Tue Sep 27 2005 - 15:33:14 EDT