On Thu, Mar 22, 2012 at 7:59 AM, Pointbreak <[email protected]> wrote: > On Sun, Mar 18, 2012, at 20:00, Igor Vaynberg wrote: >> i think there is some confusion here. wicket 1.4 had page ids. it also >> had page versions. in 1.5 we simply merged page id and page version >> into the same variable - page id. this made things much simpler and >> also allowed some usecases that were not possible when the two were >> separate. >> >> you dont have to go very far to come up with an example where page id is >> useful. >> >> 1. suppose you have a page with panel A that has a link >> 2. user hits a link on the page that swaps panel A for panel B >> 3. user presses the back button >> 4. user clicks the link on panel A >> >> now if you turn off page id and therefore page versioning it goes like >> this >> 1. wicket creates page and assigns it id 1 >> 2. page id 1 now has panel B instead of panel A >> 3. page with id 1 is rerendered >> 4. wicket loads page with id 1. user gets an error because it cannot >> find the link component the user clicked since the page has panel B >> instead of panel A >> > > This is imho not what happens with NoVersionMount. What happens is: > > 1. wicket creates page and assigns it id 1 > 2. page id 1 now has panel B instead of panel A > 3. wicket creates new page and assigns it id 2; depending on how the > page keeps state either a page with panel A and link, or a page with > Panel B is created. > > Hence, there is nothing broken in this scenario.
we were talking about something else here. the NoVersionMount has the problem of losing ajax state when the user refreshes the page. -igor > > --------------------------------------------------------------------- > 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]
