> hmmm..so correct me if its not the right understanding..i.e. the only time > wicket would be fetching the older page versions is when a user hit the back > button and clicks on a link (or submit a form) from that previous page, and > with that whatever page-version those links/forms were linked to (which > would be the original rendered page) wicket would load that page.
Yes. > That means one (ideally) wouldn't code anything himself to refer to the old > page versions lets say in the page to be rendered next, thats why i sort of > was into thinking as to why would i refer to an older version, so its only > the back button where this whole idea of version-ing comes in. The only thing you might code yourself are explicit changes. Changes in the component tree and some model (setModelObject specifically) will be recorded automatically, but property changes for instance won't be caught by Wicket. If you're not sure anything else triggers the recording of a new version, you could consider making changes explicit like for instance PageableListView#setCurrentPage does. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
