I'd say yes, but then the same object may still be in the DataContext, so
you'll end up with a duplicate... So using someting along the lines of
writeReplace() / readResolve() will likely be more appropriate.
Andrus
> Andrus Adamchik wrote:
>> Persistent properties work ok for me, and I haven't dug any deeper. I
>> can see one solution to automaticaly attach stray objects in a
>> controlled environment like (Tapestry) web application - implement
>> Externalizable and attach to the current thread DataContext on read.
>
> What is the preferred approach to attacher the data context? Simply call
> setDataContext on the data object?
>
> Thanks again,
>
> Robert
This archive was generated by hypermail 2.0.0 : Tue Mar 08 2005 - 16:57:59 EST