Hi Chris,
Maybe it is because you are adding the timer to the label and later on
replacing it is another component. Then the second AJAX round trip to the
page will look for the AbstractAjaxTimerBehavior associated to the message
component, but the new one does not have associated such a
: AbstractAjaxTimerBehavior causes exception
Hi Chris,
Maybe it is because you are adding the timer to the label and later on
replacing it is another component. Then the second AJAX round trip to the
page will look for the AbstractAjaxTimerBehavior associated to the
message
component
On Wed, 2009-11-11 at 09:21 +0100, Giambalvo, Christian wrote:
Hi all,
maybe i found a bug.
Don't know if I'm doing something wrong.
But it's a simple usecase.
Following code produces an exception:
public class HomePage extends WebPage {
private static
Betreff: Re: AbstractAjaxTimerBehavior causes exception
On Wed, 2009-11-11 at 09:21 +0100, Giambalvo, Christian wrote:
Hi all,
maybe i found a bug.
Don't know if I'm doing something wrong.
But it's a simple usecase.
Following code produces an exception:
public class
: Mittwoch, 11. November 2009 10:15
An: users@wicket.apache.org
Betreff: Re: AbstractAjaxTimerBehavior causes exception
Well I think it all boils down to the explanation a gave on my first
e-mail:
if you replace the component with a new one that does not have the behavior
then you will get
: Ernesto Reinaldo Barreiro [mailto:reier...@gmail.com]
Gesendet: Mittwoch, 11. November 2009 10:15
An: users@wicket.apache.org
Betreff: Re: AbstractAjaxTimerBehavior causes exception
Well I think it all boils down to the explanation a gave on my first
e-mail:
if you replace the component
