You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Cristi Manole <cr...@gmail.com> on 2008/03/11 19:21:09 UTC

Prevent Ajax from expiring

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

Re: Prevent Ajax from expiring

Posted by Igor Vaynberg <ig...@gmail.com>.
On Tue, Mar 11, 2008 at 11:49 AM, Cristi Manole <cr...@gmail.com> wrote:
> it expired way earlier than that.. .that's why i figured it was something
>  inside wicket...
>
>  any ideas?

not without a reproduceable usecase

-igor

>
>  Cristi
>
>  On Tue, Mar 11, 2008 at 8:39 PM, Igor Vaynberg <ig...@gmail.com>
>  wrote:
>
>
>
>  > session time out is controlled in web.xml
>  >
>  > -igor
>  >
>  >
>  > On Tue, Mar 11, 2008 at 11:21 AM, Cristi Manole <cr...@gmail.com>
>  > 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: users-unsubscribe@wicket.apache.org
>  > For additional commands, e-mail: users-help@wicket.apache.org
>  >
>  >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Prevent Ajax from expiring

Posted by Cristi Manole <cr...@gmail.com>.
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 <ig...@gmail.com>
wrote:

> session time out is controlled in web.xml
>
> -igor
>
>
> On Tue, Mar 11, 2008 at 11:21 AM, Cristi Manole <cr...@gmail.com>
> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: Prevent Ajax from expiring

Posted by Igor Vaynberg <ig...@gmail.com>.
session time out is controlled in web.xml

-igor


On Tue, Mar 11, 2008 at 11:21 AM, Cristi Manole <cr...@gmail.com> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org