BTW, is it easy to control what wicket stores in session? May be by patching wicket code? P.S. Sorry if the question is lame, I have just started studying wicket and I want to decide whether to use it in production.
> > When profiling the application server, we found out that there are HTTP > > sessions that consume up to 2 MB of memory, mostly because there are very > > large ListViews with up to 1000 entries, where each entry consumes about > 2 > > KB. >
