Sounds weird about two divs with same id.
At first glance, it looks like a bug.
Can someone confirm ?
2011/5/3 jeross jr...@greenenergycorp.com
Thank you for your quick reply.
I had the modalWindow.setOutputMarkupId(true) as well as on the message
label on the modalWindow. I tried the
In onPostProcessTarget :
timerTarget.add(modalWindow)
You have to add components you are refreshing to the AjaxRequestTarget instance.
Don't forget to set markupId to true for modalWindow
modalWindow.setMarkupId(true);
when you add it to the parent component.
2011/5/3 jeross
So, running Tomcat only (on port 80) without Apache2 does not seem an option
to me.
What about using mod_jk ?
http://tomcat.apache.org/connectors-doc/
http://tomcat.apache.org/tomcat-3.3-doc/mod_jk-howto.html
--
Isammoc
-
I agree with Matthias :
FF4 for windows (under windows 7 x32)
All ModalWindows work perfectly
But a GET request for http://:/; is sent
2011/4/11 Gabriel Landon glan...@piti.pf
I'm using wicket =1.4.15 with FF4 for windows (under windows 7 x64) and
all
the ModalWindows work perfectly (both
Thanks to you two,
2011/4/3 Martin Grigorov mgrigo...@apache.org:
Or org.apache.wicket.markup.html.ServerTimeFilter
I think it is what I was looking for.
But I think I will create my own IResponseFilter, in a similar way,
but to modify something else that head.
On Sun, Apr 3, 2011 at 5:34 AM,
Hi all,
I would like to display a footer with the time spent to generate the page.
How can I do something like generated in 0.123s ?
Timestamp difference between start and end of the Page constructor is
obviously not the solution.
And I didn't find anything in Nabble... (815 answer for time
Hi,
I don't really understand why you have two xxxApplication.java for only two
links.
In my mind, I would make only one xxxApplication.java for both pages.
But I assume is for test purpose about sharing connection information
between two (or more) distinct applications.
This problem is common :
After reading your preceding mails again, I think I get the point :
You don't need to create two classes that extends WebApplication
because you want two pages to allow authentication.
Both authentication pages are parts of the same application (read
WebApplication).
As Michael O'Cleirigh said :
