Hi, I think Page.renderCount is what stops the storing of the values. This flag indicates that the page the user uses is stale, i.e. there is another render of the same page happened after. The actual check is in PageProvider class.
I don't see any clean solution for now. What should happen if the user opens an edit page for the same entity in two tabs ? For example she saves some changes in tab2 and then goes to tab1 makes another changes and tries to save them too ? I guess you will want to abort the second save because it works with stale data. On Thu, Oct 27, 2011 at 7:51 AM, Charlie Midtlyng <[email protected]> wrote: > > We are developing an application with forms and currently using wicket > 1.4.18. > > There are primarily two issues that we are struggeling with when upgrading > to wicket 1.5.2. > > Let's say we open Page A in two tabs, first Tab1 and then Tab2. If we fill > the form in Tab1 and submit it will be valid data, but they are not stored > on our models. > However, if we fill in form in Tab2 they are stored since this tab has a > higher version number than Tab1. > > More or less the same issue exists when using back-button. Open PageA, fill > in the form and submit. Use back-button and change values and submit. The > new values are not stored on the models. In our case it would have been > better if the version number increased when using the back-button. > > Is it supposed to work in 1.5.2, and are there some special settings one > must be aware of? > > Charlie > > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
