Hi!
I have a BasePage with a SignedInPanel and SignedOutPanel. Visibility is
determined according to the apps internal login state AND async javascript
call (external login service). This is done in onConfigure method in
BasePage like this:
@Override
protected void onConfigure() {
Yes! That was it. New version deployed, everybody happy. Thank you very much,
Sir.
Sometimes Wicket can be so.. subtle. :)
Kind regards
Terje
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Panel-visibility-with-AJAX-problem-tp4671307p4671327.html
Sent from the
In trying to migrate from wicket 1.4 to 1.5, all my setResponsePage calls
get red in Eclipse. e.g:
setResponsePage(WelcomePage.class, parameters);
gets the error message:
The method setResponsePage(ClassC, PageParameters) in the type Component
is not applicable for the arguments
Thanks, yeah I figured it was still there. It was the packet-structure that
didin`t update correctly. What before was:org.apache.wicket.PageParameters
is now: org.apache.wicket.request.mapper.parameter.PageParameters
appearently.
--
View this message in context:
