Hi Nick, I prefer the same approach as you, because my domain model is rich and gives me direct feedback of what goes wrong when somebody wants to change the model state. This works well for editing simple domain objects, but one of the challenges I'm facing now is: how do I implement multiaction edits that are not directly propagated to the database? Again I take the good old Order/OrderLine example, where I want to add and remove lines at will, and finally commit them in the DB (or let the user cancel it). I asked a similar question a few days ago, and someone suggests using the Memento pattern, which I'm implementing now.
My question to you is: how do you approach this scenario? 2008/2/14, Nick Heudecker <[EMAIL PROTECTED]>: > > I always use business objects as my model objects unless the data is some > form of aggregate, like a summary table. > -- Martijn Lindhout JointEffort IT Services http://www.jointeffort.nl [EMAIL PROTECTED] +31 (0)6 18 47 25 29
