My experience with Tapestry (4 & 5) serializing a DataObject to the HTML (which it does by default when you have a loop in a form) is that the deserializing of the DataObject (on the subsequent request/response) gives you a DataObject that is disassociated from the DataContext (not good). Perhaps if the DataContext went along for the ride all would be well ...
Thanks, mrg On Wed, May 5, 2010 at 4:53 PM, Mike Kienenberger <[email protected]> wrote: > No direct experience, but I know you can serialize DataObjects and I'm > 99% certain you can serialize DataContexts. I think I did this in > one project in the past to preserve state between requests rather than > saving state in the sessions. > > On Wed, May 5, 2010 at 4:37 PM, Michael Gentry <[email protected]> wrote: >> Someone on another project here asked me if Cayenne works with session >> replication (with 1+ user DataContext objects in the HttpSession) >> between application servers (such as JBoss). They have a project >> where they are running N instances of JBoss and they replicate/sync >> the session data across the JBoss instances. They are curious if the >> DataContext + DataObjects will replicate correctly. I've never >> attempted to do so and am not sure. Does anyone have experience with >> this? >> >> Thanks! >> >> mrg >> >
