Hi,
Just put a breakpoint in your constructor and see what are the stacktraces.
On Sun, Jan 20, 2013 at 6:27 PM, kamiseq kami...@gmail.com wrote:
hi,
I try to understand why wicket (in 6th version) is constructing my page
always 3 times per every request. it is page constructor is called 3
I did, I dont see anything specific about this
java.lang.RuntimeException: test
at com.myapp.Page1.initialize(Page1.java:80)
at com.myapp.Page1.init(Page1.java:48)
at com.myapp.Page1.init(Page1.java:42)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Wasn't there some problem with empty images (img src= ) and IE
reloading the page? At least I remember some old threads on this topic.
On Mon, Jan 21, 2013 at 8:07 PM, kamiseq kami...@gmail.com wrote:
I did, I dont see anything specific about this
java.lang.RuntimeException: test
at
I have something like this in logs, I will try remove it
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
On 21 January 2013 20:12, Ernesto Reinaldo Barreiro reier...@gmail.comwrote:
Wasn't there some problem with empty images (img src= ) and IE
yep that was it, why this happens?
thanks ernesto, it is not only on IE ;] firefox also
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
On 21 January 2013 20:36, kamiseq kami...@gmail.com wrote:
I have something like this in logs, I will try
Hi,
On Mon, Jan 21, 2013 at 8:42 PM, kamiseq kami...@gmail.com wrote:
yep that was it, why this happens?
To be honest I do not know the exact reason... I guess a second request is
launched to retrieve missing empty image... Just googled for it and
found this.
ok, thanks anyway, indeed it was killing me for some time now ;]
pozdrawiam
Paweł Kamiński
kami...@gmail.com
pkaminski@gmail.com
__
On 21 January 2013 21:13, Ernesto Reinaldo Barreiro reier...@gmail.comwrote:
Hi,
On Mon, Jan 21, 2013 at 8:42 PM, kamiseq
