If you want to see the impact of serialization, turn on some debugging info:
log4j.logger.wicket.protocol.http.WebSession=DEBUG serializes state and dumps results of that just like it would do in a clustered (with the heaviest variant, HTTP session replication) environment. log4j.logger.wicket.version=DEBUG logs the whole versioning stuff. In general, it is a good idea to turn versioning off for pages that don't need it. Users won't be able to use the back button then, but in a graceful way: when versioning is turned off, the urls keep stable and thus when you push the back button, you will go to the previous 'stable' url (though I think Operah behaved a bit different...) Versioning basically records any state changes - could be model changes, but also component properties (see for instance PageableListView.CurrentPageChange, so that when a user pushes the back button and e.g. submits a form, the server side state can be rolled back again to the version that corresponds with what the user sees in his browser. Re: annonymous classes. Annonymous classes are not reccomended per se. It is nice that they hide implementation details, but I prefer to use (static) inner classe for this. And in fact, I usually like to try to make reusable models, and put them in a seperate package as public classes. From my experience every application will have lots of opportunities for reusing models in many places. Eelco ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
