Thanks a lot for that, James. From that thread (http://forum.hibernate.org/viewtopic.php?t=958965), Hibernate's "Object Session.merge(Object)" method looks like a viable option; it was originally called "Object saveOrUpdateCopy(Object)" -- it returns the persisted object if the transaction is successful, otherwise it returns the original object. i.e. it essentially carries out that "memory-transaction" we've been discussing.
I'm certainly going to examine the UI-data-buffer suggestion as a way of making my page classes clearer in some cases (e.g. if I'm not editing an /entire/ entity, it's a little misleading for the page to have the entire entity as a property), but since I'm halfway into my current project it's nice that I won't have to perform major surgery on my design methodology up to this point. I really appeciate everyone's help and advice, Jim -----Original Message----- From: James Carman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 03, 2006 11:29 AM To: 'Tapestry users' Subject: RE: Insert/Update pages and Hibernate Well, I just posted it to the forum too. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
