Re: Wicket and tomcat cluster

2013-03-29 Thread Marios Skounakis
Dan, thanks for you answer. As you said, with the default implementation of DiskDataStore only the most recent page is kept in the session state and available on all servers. So are using non-sticky sessions and having a stateful page open a modal window with a new stateful page will not work.

Re: Wicket and tomcat cluster

2013-03-29 Thread Dan Retzlaff
If you go non-sticky you'll need to experiment with RenderStrategy. Each has it's pros and cons, and I don't have experience to advise you further. Yes if you want the user to interact with more than one page at a time you'll need to make sure they're all available. You'll also need to replicate

Re: Wicket and tomcat cluster

2013-03-29 Thread Marios Skounakis
Thanks, things are a lot clearer for me now. On Fri, Mar 29, 2013 at 4:28 PM, Dan Retzlaff dretzl...@gmail.com wrote: If you go non-sticky you'll need to experiment with RenderStrategy. Each has it's pros and cons, and I don't have experience to advise you further. Yes if you want the user

Re: Wicket and tomcat cluster

2013-03-28 Thread Dan Retzlaff
Hi Marios, This behavior is determined by IDataStore interface. DiskDataStore is used by default, so only the most recent page is kept in the session (and available for failover). It puts page history into a directory specified in javax.servlet.context.tempdir servlet attribute (under work

Re: Wicket and tomcat cluster

2013-03-28 Thread Dan Retzlaff
Sorry I mistyped: default is REDIRECT_TO_BUFFER. On Thu, Mar 28, 2013 at 2:36 PM, Dan Retzlaff dretzl...@gmail.com wrote: Hi Marios, This behavior is determined by IDataStore interface. DiskDataStore is used by default, so only the most recent page is kept in the session (and available for