Just now I tried to use Wicket 6.9.0 instead of 6.8.0 and things looks be
working now. Now it looks to be working out for me :)
But now I have two new problems
1) On the HomePage the AJAX is not working. In the Chrome browser console I
can see /Uncaught TypeError: Cannot read property
On Wed, Jul 10, 2013 at 4:00 PM, dev your@gmail.com wrote:
Just now I tried to use Wicket 6.9.0 instead of 6.8.0 and things looks be
working now. Now it looks to be working out for me :)
But now I have two new problems
1) On the HomePage the AJAX is not working. In the Chrome browser
Hi
I am also facing similar issue, I have an application which was developed in
wicket 1.4.18 and sometime back we decided to upgrade the Wicket version to
6.8.0.
After making the making and fixing the error I found that for some reasons
my HomePage is getting instantiated again and again. I
Hi,
Put a breakpoint in MyHomePage's constructor and see the stacktrace(s).
Paste them here if you are not sure how to read interpret them.
On Mon, Jul 8, 2013 at 4:29 PM, dev your@gmail.com wrote:
Hi
I am also facing similar issue, I have an application which was developed
in
wicket
Hi, here is the stacktrace..
Jul 8, 2013 8:44:07 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: C:\Program
@wicket.apache.org
Subject: Re: why is getHomePage called multiple times?
Hi, here is the stacktrace..
Jul 8, 2013 8:44:07 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found
Hi sorry for the confusion...here is the stack
Daemon Thread [http-8080-5] (Suspended (breakpoint at line 81 in HomePage))
HomePage.init(PageParameters) line: 81
NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line:
not
available [native method]
You could also print stacktrace of all invocations of the constructor by
adding this line:
new Exception().printStackTrace();
br, Edvard
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/why-is-getHomePage-called-multiple-times-tp1881852p4660161.html
Sent from the
Hi,
There is nothing wrong here.
Are all invocations of your Home page constructor with the same stack
traces ?
On Mon, Jul 8, 2013 at 8:05 PM, dev your@gmail.com wrote:
Hi sorry for the confusion...here is the stack
Daemon Thread [http-8080-5] (Suspended (breakpoint at line 81 in
Jason, the method getHomePage#MyWicketApplication only return the Class of
your application home page, an call from Wicket to it's method, doesn't
means that an instance of HomePage will to be generated.
This is a code from WebRequestCodingStrategy for example:
if
Any chance you have empty image src attributes in your home page?
On Mon, Aug 31, 2009 at 9:19 PM, Jason Novotny jason.novo...@gmail.comwrote:
Hi,
My home page takes longer to load than expected and after placing a log
line in getHomePage#MyWicketApplication I see that it's being called 3
Hi Nick,
I tried with the simplest page:
html xmlns=http://www.w3.org/1999/xhtml;
xmlns:wicket=http://www.w3.org/1999/xhtml;
head
/head
body
hello wicket
/body
/html
The good news is that it only happens after loading the app for the
first time-- after an additional request is made to
I have the same issue. Same message appear twice in tomcat log:
2009-09-01 13:04:52,009 INFO [Application] [HelloWorldApplication] init:
Wicket core library initializer
2009-09-01 13:04:52,009 INFO [Application] [HelloWorldApplication] init:
Wicket core library initializer
2009-09-01
13 matches
Mail list logo
