i would just fix the serialization exceptions So that you can cluster when you want to or you can restart your server without loosing sessions
HttpSessionStore does have its problems because of the stack it keeps (with use of backbutton) johan On Tue, Mar 4, 2008 at 1:15 PM, richardwilko <[EMAIL PROTECTED]> wrote: > > Hi, > > Could someone please explain (or point me in the direction of a tutorial) > the difference between HttpSessionStore and SecondLevelCacheSessionStore. > We have to use a HttpSessionStore, because otherwise we get > NotSerializableException's being thrown everywhere. > > Does using HttpSessionStore have any drawbacks? We do have some problems > with illegal argument exceptions being thrown when I try to use ajax on > some > (but not all) panels, and get session expired errors more often than I > would > like. could this have anything to do with the type of session store? > > Thanks, > > Richard > -- > View this message in context: > http://www.nabble.com/Confused-about-different-session-stores-tp15825950p15825950.html > Sent from the Wicket - User mailing list archive at > Nabble.com<http://nabble.com/> > . > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
