The nice thing - which we didn't have in the past - of turning it off, is that the backbutton won't even take you to the former version of the page, as the URL is the same.
Eelco On 9/6/05, Johan Compagner <[EMAIL PROTECTED]> wrote: > then by default the back button doesn't work out of the box. > I do like to have it by default on component changes. (add/remove or > internalstate change) > but model change is a thing i can live without by default. > Because most of the time it is db data. > And if you alter an object and then go back then revering the data in > wicket doesn't make sense > (because the data in the db is changed anyway) > But ofcourse when scrolling though a list and then go back once. Then i > do want to make sure > that when i edit that one i edit the right one.. > (and not the latest one i just had in front of me before i did go back) > > I think default on is better. Only we have to have a invalidate on the > page so that is > immediately expired.... (then you shouldn't redirect to that same page > ofcourse because then it is added back) > > johan > > > Eelco Hillenius wrote: > > I've been thinking about the whole versioning thing longer actually: > > wouldn't it be a better (certainly more efficient) default to turn it > > off? If you really want the rollback behaviour, you can easily turn it > > on. > > > > Eelco > > > > > > On 9/6/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > >> Versioning should work out-of-the-box and roll back changes. A lot of > >> times this is not what you want though. Your best option then is to > >> turn off versioning, by overriding method isVersioned and let it > >> return false (e.g. on your Page). This additionally has the effect > >> that your url won't change, so pushing the backbutton won't direct the > >> user to the page with the former form values anyway. > >> > >> Eelco > >> > >> On 9/6/05, Ingram Chen <[EMAIL PROTECTED]> wrote: > >> > >>> A simple submission flow: > >>> > >>> PageA -> submit -> PageB > >>> > >>> When a user clicks "Back Button" to back PageA, > >>> How to prevent PageA to re-submit and redirect to expired Page for the > >>> user > >>> ? > >>> > >>> I know every page has version but can't figure out how to do that.... > >>> > >>> Thanks in advance. > >>> > >>> -- > >>> Ingram Chen > >>> Java [EMAIL PROTECTED] > >>> Institue of BioMedical Sciences Academia Sinica Taiwan > >>> blog: http://www.javaworld.com.tw/roller/page/ingramchen > >>> > > > > > > ------------------------------------------------------- > > SF.Net email is Sponsored by the Better Software Conference & EXPO > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
