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 final long serialVersionUID = 1L;
private static int testCounter = 0;
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
Chris
-Ursprüngliche Nachricht-
Von: Ernesto Reinaldo Barreiro [mailto:reier...@gmail.com]
Gesendet: Mittwoch, 11. November 2009 09:35
An: users@wicket.apache.org
Betreff: Re: AbstractAjaxTimerBehavior causes exception
Hi Chris,
Maybe it is because you are adding the timer to the label
in.
Greets Chris
-Ursprüngliche Nachricht-
Von: Ernesto Reinaldo Barreiro [mailto:reier...@gmail.com]
Gesendet: Mittwoch, 11. November 2009 09:35
An: users@wicket.apache.org
Betreff: Re: AbstractAjaxTimerBehavior causes exception
Hi Chris,
Maybe it is because you are adding the timer
. November 2009 09:39
An: users@wicket.apache.org
Betreff: AW: AbstractAjaxTimerBehavior causes exception
Hi Ernesto,
the label was just an example.
In my app i try to replace the navigation (you remember your suggestion
with a timer?)
The navigation is a panel. So recreate the whole panel
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
...@e-card.bg]
Gesendet: Mittwoch, 11. November 2009 09:59
An: users@wicket.apache.org
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
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
: 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 an exception (the same will happend if you remove the
behavior during a round
: 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
to the page.
That’s why there is Component#replaceWith(Component).
Greets
-Ursprüngliche Nachricht-
Von: Martin Grigorov [mailto:mcgreg...@e-card.bg]
Gesendet: Mittwoch, 11. November 2009 09:59
An: users@wicket.apache.org
Betreff: Re: AbstractAjaxTimerBehavior causes exception
On Wed
...@excelsisnet.com]
Gesendet: Mittwoch, 11. November 2009 10:24
An: users@wicket.apache.org
Betreff: AW: AbstractAjaxTimerBehavior causes exception
You're right Ernesto, your example works, but what if I want to replace a
whole panel and not just the model of a label?
-Ursprüngliche Nachricht-
Von
: 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
13 matches
Mail list logo
