I think we can solve serialization problems... CDO should be
reattached indirectly inside DataContext.readObject(..). I am
surprised that didn't work for PersistentObject. You may add a
breakpoint in DataContext.readObject(..) to see what really happens
there.
Andrus
On Nov 7, 2007, at 6:14 PM, Kevin Menard wrote:
Well, I've made marginal progress there as well. I am wrestling
with a
serialization problem right now. I know you had mentioned issues with
this earlier, but it's the object context that's behaving differently
from CayenneDataObject.
I've had a Tapestry 4 app that's used lists of CDOs in @For loops and
has just worked. As PersistentObjects, they lose their data
context on
deserialization. No custom squeezers are involved. What's really
interesting is that the contexts are marked as transient in both
CDO and
PO.
I suspect once that's squared away, the rest won't be nearly as bad.
--
Kevin
-----Original Message-----
From: Andrus Adamchik [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2007 3:53 AM
To: [email protected]
Subject: Re: Cleaning up ROP
Hi Kevin,
CayenneDataObject approach is fundamentally different from other
persistent object implementations that are all variations of POJO. So
I think a different approach may work better - using current client
objects on the server (instead of using current server objects on the
client).
Andrus
