On 8/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On 8/14/07, Alex Objelean <[EMAIL PROTECTED]> wrote: > > > > In wicket-1.2.6 I used this in order to not serialize session attributes: > > > > [CODE] > > getDebugSettings().setSerializeSessionAttributes(false); > > [/CODE] > > > > What is equivalent for this in wicket-1.3.0-beta2? > > > > Thank you! > > There is none, but if you use the default session store, just keep an > eye on your log, as you'll immediately know whether something is not > serializable. The default now is to use a sesison store that > serializes pages to a second level cache (typically a temp dir) and > only keeps the current page in RAM.
Oh wait, you want to turn it off! :) In that case, you'd better use the HttpSessionStore, by overriding newSessionStore in your application class and return that. Or return a custom in memory store. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
