Shane and Daniel Thanks for your pointers and ideas.
Shane Mingins <[EMAIL PROTECTED]> wrote on 07/06/2004 05:30:35 p.m.: > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Saturday, 5 June 2004 12:23 a.m. > > To: OJB Users List > > Subject: Handling dirty objects in a CRUD web MVC app, OJB handles object > > store. > > > > > > Question is: which is the best way to handle the dirty Object (A) and its > > collections of somehow dirty objects B. > > Is there any well know pattern to to this? What if someone has changed the > > object while the user was doing his changes in the web? > > Here we've implemented different strategies, from deleting all existing > > childs and storing the new ones to sending hidden attributes with OIDs and > > dirty flags and writing some logic to handle the changes. But, I fee we > > are not using some OJB capabilities that might do this for us. > > > > Have a look at Patterns of Enterprise Application Architecture - Martin > Fowler for some ideas. There is a pattern Unit of Work that may be of > interest. > > Shane > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
