On Wed, Aug 20, 2008 at 12:19 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Not quite true: first Wicket will attach the model, which will load > the data from the database. When the form input is valid, this data > will be propagated to the attached model. => the data will reflect the > input.
If you don't commit the changes (and you wouldn't want to typically in a wizard) to the object between "pages", then the original data will merely be loaded from the database and your previous edits will be lost. > > The problem is that you don't want to persist the modified input > between the wizard steps. IIUC the OSIV filter will commit the changes > between the steps when the entity was changed. You typically only want > this to happen at the last step of the wizard. The OSIV won't commit the changes, because there's no transaction around it (the default flush mode is "NEVER"). OSIV merely opens a session. It doesn't commit any changes at the end of the request. It implements session-per-request, not transaction-per-request. > > This discussion is of course completely moot when you don't have a > persistent entity as your model for the wizard. Of course, but then again why would you be using LDM if you're not editing a persistent entity? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
