You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Adriano dos Santos Fernandes <ad...@gmail.com> on 2009/02/12 17:50:40 UTC
AbstractAjaxTimerBehavior / Firefox / Page constructor
I've a simple page as below, and when I call it from Firefox, ReportPage
constructor is almost always called two times. Some times it's correctly
called once. What may be wrong?
public class ReportPage extends WebPage
{
private static final long serialVersionUID = 1L;
private static final int CHECK_INTERVAL = 2; // segundos
public ReportPage(PageParameters parameters)
{
super(parameters);
WebMarkupContainer update = new WebMarkupContainer("update");
add(update);
update.add(new
AbstractAjaxTimerBehavior(Duration.seconds(CHECK_INTERVAL)) {
private static final long serialVersionUID = 1L;
@Override
protected void onTimer(AjaxRequestTarget target)
{
}
});
}
}
Adriano
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Sorry - I should've been more clear. Images work fine with timers.
Specifically, I was asking if your page had any img tags that had an empty
source - that causes similar behavior.
--
Jeremy Thomerson
http://www.wickettraining.com
On Sat, Feb 14, 2009 at 8:25 AM, Adriano dos Santos Fernandes <
adrianosf@gmail.com> wrote:
> I know I have, but could only test about it on Monday. Is there any
> workaround, to have the timer and the image together?
>
> Thanks,
>
>
> Adriano
>
>
>
> Jeremy Thomerson wrote:
>
>> Have you made sure that you don't have any <img src="" ... /> in your
>> code?
>> This has been known to cause similar behavior.
>>
>> On Thu, Feb 12, 2009 at 11:45 AM, Adriano dos Santos Fernandes <
>> adrianosf@gmail.com> wrote:
>>
>>
>>
>>> Thomas Mäder escreveu:
>>>
>>>
>>>
>>>> Why don't you put a breakpoint in the constructor and see let us know
>>>> what
>>>> you find out? Is the constructor called through the same stack trace
>>>> twice?
>>>>
>>>>
>>>>
>>> The constructor is called by the filter, it's another request from the
>>> browser. The first URL is the entered one, and the second has a new
>>> parameter about wicket pagemap. The page is a bookmarkable.
>>>
>>> I haven't succeed to debug with Firebug.
>>>
>>>
>>>
>>> Adriano
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Adriano dos Santos Fernandes <ad...@gmail.com>.
I know I have, but could only test about it on Monday. Is there any
workaround, to have the timer and the image together?
Thanks,
Adriano
Jeremy Thomerson wrote:
> Have you made sure that you don't have any <img src="" ... /> in your code?
> This has been known to cause similar behavior.
>
> On Thu, Feb 12, 2009 at 11:45 AM, Adriano dos Santos Fernandes <
> adrianosf@gmail.com> wrote:
>
>
>> Thomas Mäder escreveu:
>>
>>
>>> Why don't you put a breakpoint in the constructor and see let us know what
>>> you find out? Is the constructor called through the same stack trace
>>> twice?
>>>
>>>
>> The constructor is called by the filter, it's another request from the
>> browser. The first URL is the entered one, and the second has a new
>> parameter about wicket pagemap. The page is a bookmarkable.
>>
>> I haven't succeed to debug with Firebug.
>>
>>
>>
>> Adriano
>>
>>
>> ---------------------------------------------------------------------
>> 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: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Jeremy Thomerson <je...@wickettraining.com>.
Have you made sure that you don't have any <img src="" ... /> in your code?
This has been known to cause similar behavior.
On Thu, Feb 12, 2009 at 11:45 AM, Adriano dos Santos Fernandes <
adrianosf@gmail.com> wrote:
> Thomas Mäder escreveu:
>
>> Why don't you put a breakpoint in the constructor and see let us know what
>> you find out? Is the constructor called through the same stack trace
>> twice?
>>
> The constructor is called by the filter, it's another request from the
> browser. The first URL is the entered one, and the second has a new
> parameter about wicket pagemap. The page is a bookmarkable.
>
> I haven't succeed to debug with Firebug.
>
>
>
> Adriano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Jeremy Thomerson
http://www.wickettraining.com
Re: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Adriano dos Santos Fernandes <ad...@gmail.com>.
Johan Compagner escreveu:
> That settings just triggers some code that checks if the pagemap name
> is equal to the window name if that isnt the case then it does a
> redict to a new page so that every browser window has its own pagemap
>
> Why do you have that setting enabled? With the disk store it is not
> really needed anymore
The problem gone away removing this setting, thanks!
My page is very simple, with one <img wicket:id="loading" /> tag (i.e.,
src is not empty).
Adriano
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Adriano dos Santos Fernandes <ad...@gmail.com>.
I had some issue when opening multiple tabs. But I should revisit this,
because my page was with a serialization problem this time.
Adriano
Johan Compagner wrote:
> That settings just triggers some code that checks if the pagemap name
> is equal to the window name if that isnt the case then it does a
> redict to a new page so that every browser window has its own pagemap
>
> Why do you have that setting enabled? With the disk store it is not
> really needed anymore
>
> On 13/02/2009, Adriano dos Santos Fernandes <ad...@gmail.com> wrote:
>
>> Johan Compagner escreveu:
>>
>>> if that happens then the newWindowBrowser detection is enabled and
>>> executed.
>>> This makes sure that a new tab or browser window (but same session) will
>>> have there own pagemap
>>>
>> I have "getPageSettings().setAutomaticMultiWindowSupport(true)". But why
>> AbstractAjaxTimerBehavior would cause a redirection (I see the new url
>> with the wicket:pageMapName/wicket-N in the browser). And each time I
>> enter in the page, N is incremented. May be something wrong on wicket
>> javascripts?
>>
>>
>> Adriano
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Johan Compagner <jc...@gmail.com>.
That settings just triggers some code that checks if the pagemap name
is equal to the window name if that isnt the case then it does a
redict to a new page so that every browser window has its own pagemap
Why do you have that setting enabled? With the disk store it is not
really needed anymore
On 13/02/2009, Adriano dos Santos Fernandes <ad...@gmail.com> wrote:
> Johan Compagner escreveu:
>> if that happens then the newWindowBrowser detection is enabled and
>> executed.
>> This makes sure that a new tab or browser window (but same session) will
>> have there own pagemap
> I have "getPageSettings().setAutomaticMultiWindowSupport(true)". But why
> AbstractAjaxTimerBehavior would cause a redirection (I see the new url
> with the wicket:pageMapName/wicket-N in the browser). And each time I
> enter in the page, N is incremented. May be something wrong on wicket
> javascripts?
>
>
> Adriano
>
>
> ---------------------------------------------------------------------
> 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: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Adriano dos Santos Fernandes <ad...@gmail.com>.
Johan Compagner escreveu:
> if that happens then the newWindowBrowser detection is enabled and executed.
> This makes sure that a new tab or browser window (but same session) will
> have there own pagemap
I have "getPageSettings().setAutomaticMultiWindowSupport(true)". But why
AbstractAjaxTimerBehavior would cause a redirection (I see the new url
with the wicket:pageMapName/wicket-N in the browser). And each time I
enter in the page, N is incremented. May be something wrong on wicket
javascripts?
Adriano
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Johan Compagner <jc...@gmail.com>.
if that happens then the newWindowBrowser detection is enabled and executed.
This makes sure that a new tab or browser window (but same session) will
have there own pagemap
On Thu, Feb 12, 2009 at 18:45, Adriano dos Santos Fernandes <
adrianosf@gmail.com> wrote:
> Thomas Mäder escreveu:
>
>> Why don't you put a breakpoint in the constructor and see let us know what
>> you find out? Is the constructor called through the same stack trace
>> twice?
>>
> The constructor is called by the filter, it's another request from the
> browser. The first URL is the entered one, and the second has a new
> parameter about wicket pagemap. The page is a bookmarkable.
>
> I haven't succeed to debug with Firebug.
>
>
>
> Adriano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Adriano dos Santos Fernandes <ad...@gmail.com>.
Thomas Mäder escreveu:
> Why don't you put a breakpoint in the constructor and see let us know what
> you find out? Is the constructor called through the same stack trace twice?
The constructor is called by the filter, it's another request from the
browser. The first URL is the entered one, and the second has a new
parameter about wicket pagemap. The page is a bookmarkable.
I haven't succeed to debug with Firebug.
Adriano
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AbstractAjaxTimerBehavior / Firefox / Page constructor
Posted by Thomas Mäder <th...@devotek-it.ch>.
Why don't you put a breakpoint in the constructor and see let us know what
you find out? Is the constructor called through the same stack trace twice?
Thomas
On Thu, Feb 12, 2009 at 5:50 PM, Adriano dos Santos Fernandes <
adrianosf@gmail.com> wrote:
> I've a simple page as below, and when I call it from Firefox, ReportPage
> constructor is almost always called two times. Some times it's correctly
> called once. What may be wrong?
>
> public class ReportPage extends WebPage
> {
> private static final long serialVersionUID = 1L;
> private static final int CHECK_INTERVAL = 2; // segundos
>
> public ReportPage(PageParameters parameters)
> {
> super(parameters);
>
> WebMarkupContainer update = new WebMarkupContainer("update");
> add(update);
> update.add(new
> AbstractAjaxTimerBehavior(Duration.seconds(CHECK_INTERVAL)) {
> private static final long serialVersionUID = 1L;
>
> @Override
> protected void onTimer(AjaxRequestTarget target)
> {
> }
> });
> }
> }
>
>
> Adriano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Thomas Mäder
Wicket & Eclipse Consulting
www.devotek-it.ch