> In your opinion. Hibernate supports merging (if that's what you're using). > Why not edit the object in a detached state (not in the session)? > Then, when you want to update it, you call update()?
If there was only one simple object yes... but there is a whole collaboration diagram of objects. Keeping the state of what is actually updated by the user and what has only default values would just result in a jungle of hard-to-debug bugs... > write a model that returns your default value in getobject and updates > the object in setobject This sounds good in principle, but how do I know when to stop giving the default value? I will need to have a check also at setObject to turn off the default value? Still the hack sounds to me like a simpler solution: Why not give FormComponent a method formComponent.set'Default'RawValue(xx)? ** Martin > > --------------------------------------------------------------------- > 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]
