On Jan 14, 2006, at 8:41, Rick Uks wrote:
Is this approach most common? What are alternatives?
Since Tapestry will directly modify an object when the form is submitted, if you want to control exactly when the object is changed you have to have Tapestry work on through an intermediate copy.
Going back to the original question (wanting to make sure any alterations happen within a transaction), one could go ahead and let Tapestry change the data in the object, then open a transaction and do the save or update. The database won't get changed until the save/ update operation, so as long as it's wrapped in a transaction everything will be OK.
...R --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
