Re: ajax timer dying

2016-10-03 Thread Jonathan Locke
That was a pretty good guess! It's working now, thanks.

Jon


On Mon, Oct 3, 2016 at 12:28 PM, Sven Meier  wrote:

> My guess:
>
> https://issues.apache.org/jira/browse/WICKET-6191
>
> Regards
> Sven
>
>
>
> Am 03.10.2016 um 20:16 schrieb Tobias Soloschenko:
>
>> Hi,
>>
>> maybe https://ci.apache.org/projects/wicket/apidocs/6.x/org/
>> apache/wicket/util/time/Duration.html
>>
>> Duration.MAXIMUM
>>
>> kind regards
>>
>> Tobias
>>
>> Am 03.10.2016 um 20:07 schrieb Jonathan Locke :
>>>
>>> hello all,
>>>
>>> been a while! i don't quite understand the parameters of this issue i'm
>>> running into yet, but i have an AbstractAjaxTimerBehavior that i'm adding
>>> to my page in order to handle updates from asynchronous queries. it works
>>> great except that *every once in a while* the timer dies and there are no
>>> more calls to the timer behavior. has anyone run into this kind of thing?
>>> there's no javascript error on the console, so it's not that. my memory
>>> is
>>> foggy on wicket ajax... is there maybe some special debugging magic i
>>> could
>>> turn on to figure this out? is there any way to ensure that the timer
>>> never
>>> dies?
>>>
>>> thanks,
>>>
>>> jon
>>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


Re: ajax timer dying

2016-10-03 Thread Sven Meier

My guess:

https://issues.apache.org/jira/browse/WICKET-6191

Regards
Sven


Am 03.10.2016 um 20:16 schrieb Tobias Soloschenko:

Hi,

maybe 
https://ci.apache.org/projects/wicket/apidocs/6.x/org/apache/wicket/util/time/Duration.html

Duration.MAXIMUM

kind regards

Tobias


Am 03.10.2016 um 20:07 schrieb Jonathan Locke :

hello all,

been a while! i don't quite understand the parameters of this issue i'm
running into yet, but i have an AbstractAjaxTimerBehavior that i'm adding
to my page in order to handle updates from asynchronous queries. it works
great except that *every once in a while* the timer dies and there are no
more calls to the timer behavior. has anyone run into this kind of thing?
there's no javascript error on the console, so it's not that. my memory is
foggy on wicket ajax... is there maybe some special debugging magic i could
turn on to figure this out? is there any way to ensure that the timer never
dies?

thanks,

jon



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



Re: ajax timer dying

2016-10-03 Thread Tobias Soloschenko
Hi,

maybe 
https://ci.apache.org/projects/wicket/apidocs/6.x/org/apache/wicket/util/time/Duration.html

Duration.MAXIMUM

kind regards

Tobias

> Am 03.10.2016 um 20:07 schrieb Jonathan Locke :
> 
> hello all,
> 
> been a while! i don't quite understand the parameters of this issue i'm
> running into yet, but i have an AbstractAjaxTimerBehavior that i'm adding
> to my page in order to handle updates from asynchronous queries. it works
> great except that *every once in a while* the timer dies and there are no
> more calls to the timer behavior. has anyone run into this kind of thing?
> there's no javascript error on the console, so it's not that. my memory is
> foggy on wicket ajax... is there maybe some special debugging magic i could
> turn on to figure this out? is there any way to ensure that the timer never
> dies?
> 
> thanks,
> 
>jon


ajax timer dying

2016-10-03 Thread Jonathan Locke
hello all,

been a while! i don't quite understand the parameters of this issue i'm
running into yet, but i have an AbstractAjaxTimerBehavior that i'm adding
to my page in order to handle updates from asynchronous queries. it works
great except that *every once in a while* the timer dies and there are no
more calls to the timer behavior. has anyone run into this kind of thing?
there's no javascript error on the console, so it's not that. my memory is
foggy on wicket ajax... is there maybe some special debugging magic i could
turn on to figure this out? is there any way to ensure that the timer never
dies?

thanks,

jon