>> 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. :(
Is there some possibility to avoid the serialization? We have a couple of classes which have final fields initialized from the multi-arg-constructor. I just don't want to give up the final and don't want to add a (public) no-arg-constructor. 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
