> On account of the transparent login, like Martijn said if you use a > framework for your security it is already handled automagically for > you. Now i am a bit biased on the new wicket-security framework since > i wrote it :), but you should really check it out sometime.
To be exact, we don't need it for login, but for securing a download by accepting a corresponding license agreement (thanks to German laws). > On account of the serialization, yes this will become a problem for > your backbutton support. > wicket tries to serialize every page to disk and later retrieve it > when a user used the browsers backbutton and then performs an action > where it is necessary to go back to the server. Hmm, looks like I need to do that. :( The above mentioned download scenario will look like: - select the file to download (e.g. by getting a link by e-mail or by selecting it on our website) - on the file-download page check, whether the session-flag for accepted license agreement is set; if not, redirect to the license agreement page and path an IPageLink for the accept button, so the file-download page gets its right parameters after accepting the license agreement Regarding the back-button: it would be the best if the intermediate license agreement page would not occur when pressing the back-button, but instead the previous page (if any). Is something like that possible? Tom Maurice Marrink wrote: > On account of the serialization, yes this will become a problem for > your backbutton support. > wicket tries to serialize every page to disk and later retrieve it > when a user used the browsers backbutton and then performs an action > where it is necessary to go back to the server. > > On account of the transparent login, like Martijn said if you use a > framework for your security it is already handled automagically for > you. Now i am a bit biased on the new wicket-security framework since > i wrote it :), but you should really check it out sometime. > > Maurice > > On 5/28/07, Thomas Singer <[EMAIL PROTECTED]> wrote: >> Hm, by default, I'm getting an error that my page is not serializable. But >> when I set >> >> application.getDebugSettings().setSerializeSessionAttributes(false); >> >> it works without problems. Could this become a problem when my page still is >> not serializable? >> >> Tom >> >> >> Thomas Singer wrote: >>> Never mind. RestartResponseAtInterceptPageException-handling is more >>> lightweight than I assumed. Of course the other processing is completely up >>> to me. >>> >>> Tom >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Wicket-user mailing list >> Wicket-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wicket-user >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
