it expired way earlier than that.. .that's why i figured it was something inside wicket...
any ideas? Cristi On Tue, Mar 11, 2008 at 8:39 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > session time out is controlled in web.xml > > -igor > > > On Tue, Mar 11, 2008 at 11:21 AM, Cristi Manole <[EMAIL PROTECTED]> > wrote: > > Hello, > > > > I'm experiencing a strange behavior from regular ajax components (those > > included in wicket like, for example, the tree component) : on a page > > containing one (or more) such components and using it, after some time > it > > will stop working, meaning it will not do anything (for example > clicking on > > the + in a ajax tree component stops doing anything). > > > > Is this because the page expires in the "background" so to speak? How > can I > > set a longer expiration period or disable it all together? > > > > I'm deploying to Tomcat and I tested it in IE and FF. > > > > Tks, > > Cristi > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
