On Thu, Jul 24, 2008 at 10:06 AM, Fabrizio Giudici < [EMAIL PROTECTED]> wrote:
> > On Jul 24, 2008, at 8:58 , Johan Compagner wrote: > > Its not just wicket who expects serializable.. >> A webcontainer also expects every thing in the http session to be >> serializeable and not just for clustering.. Also for restarts or the >> > > AFAIK it's not true: J2EE application *may* ask for serialization if you > enable some kind of clustering in the webserver. But above all that happens > for the *session*, not for each datum I manage :-) no this is not true. Tomcat, the default tomcat installation, already uses serialization by default. Of course not when you run, but if you for example want to upgrade a webapp or have to restart tomcat quickly then it will use serialization. And this has nothing to do with clustering. I have seen so many serialization errors in my live with all kind of different servers (tomcat/resin) without the usage of clustering.. > >> container could flush idle session to disk to conserve memory. >> >> And wicket only wants it if you use the diskpagestore so if you dont >> use that then wicket doesnt really care >> > > AFAIK (but here with higher margins of error) you can't avoid the use of > the diskpagestore on Wicket 1.4. httpsessionstore does work but has its drawbacks yes. And those can really only be solved by using serialization because we need to be able to create clones Or you as a developer disable page versioning on all your pages and then just use the back button for pages itself and make a simple store that just keeps 5 pages in history or something like that. johan
