Problems upgrading from 7.4.0 to 7.5.0
Hi all, I am trying to upgrade the Apache Syncope console from 7.4.0 to recent 7.5.0, but I am experiencing some troubles. First, I had to remove from [1], since Wicket was complaining that the element had to be closed (?): now things are working fine again (as it used to do up to 7.4.0), but I honestly do not understand why. Now I am getting [2] and AFAIU this depends on the fact that the WebSocketSettings I am using in [3] have a null or empty 'filterPrefix': again, this works perfectly fine with 7.4.0. Any hint? Thanks. Regards. [1] https://github.com/apache/syncope/blob/2_0_X/client/console/src/main/resources/org/apache/syncope/client/console/pages/Login.html#L58-L59 [2] https://paste.apache.org/YSzq [3] https://github.com/apache/syncope/blob/2_0_X/client/console/src/main/java/org/apache/syncope/client/console/pages/BasePage.java#L91 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems upgrading from 7.4.0 to 7.5.0
Hi, On Thu, Oct 27, 2016 at 10:28 AM, Francesco Chicchiriccò < ilgro...@apache.org> wrote: > Hi all, > I am trying to upgrade the Apache Syncope console from 7.4.0 to recent > 7.5.0, but I am experiencing some troubles. > > First, I had to remove > > > > from [1], since Wicket was complaining that the element had to be > closed (?): now things are working fine again (as it used to do up to > 7.4.0), but I honestly do not understand why. > What do you mean by "now it works fine" ? How do you get the i18n-ed value of "submit" now ? > > Now I am getting [2] and AFAIU this depends on the fact that the > WebSocketSettings I am using in [3] have a null or empty 'filterPrefix': > again, this works perfectly fine with 7.4.0. > Please file a bug for [2]. It is a regression. Most probably [1] is also a bug but I have to try it. Please create a ticket for it too. Thanks! > > Any hint? Thanks. > Regards. > > [1] https://github.com/apache/syncope/blob/2_0_X/client/ > console/src/main/resources/org/apache/syncope/client/ > console/pages/Login.html#L58-L59 > [2] https://paste.apache.org/YSzq > [3] https://github.com/apache/syncope/blob/2_0_X/client/ > console/src/main/java/org/apache/syncope/client/console/ > pages/BasePage.java#L91 > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Problems upgrading from 7.4.0 to 7.5.0
Hi, [1] does your button have a model object? Since WICKET-6225 the model object is used to replace the component body, iff you're using a tag. Previously the model object was used for the value of an tag only. Regards Sven Am 27.10.2016 um 10:28 schrieb Francesco Chicchiriccò: Hi all, I am trying to upgrade the Apache Syncope console from 7.4.0 to recent 7.5.0, but I am experiencing some troubles. First, I had to remove from [1], since Wicket was complaining that the element had to be closed (?): now things are working fine again (as it used to do up to 7.4.0), but I honestly do not understand why. Now I am getting [2] and AFAIU this depends on the fact that the WebSocketSettings I am using in [3] have a null or empty 'filterPrefix': again, this works perfectly fine with 7.4.0. Any hint? Thanks. Regards. [1] https://github.com/apache/syncope/blob/2_0_X/client/console/src/main/resources/org/apache/syncope/client/console/pages/Login.html#L58-L59 [2] https://paste.apache.org/YSzq [3] https://github.com/apache/syncope/blob/2_0_X/client/console/src/main/java/org/apache/syncope/client/console/pages/BasePage.java#L91 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems upgrading from 7.4.0 to 7.5.0
On 2016-10-27 11:30 (+0200), Sven Meier wrote: > Hi, > > [1] does your button have a model object? Yes, it does. > Since WICKET-6225 the model object is used to replace the component > body, if you're using a tag. > Previously the model object was used for the value of an tag only. Ah, now it makes sense, thanks. I would suggest adding this to the 7.5.0 release notes, which pretend it to be a "drop-in replacement". Regards. > Am 27.10.2016 um 10:28 schrieb Francesco Chicchiricc: > > Hi all, > > I am trying to upgrade the Apache Syncope console from 7.4.0 to recent > > 7.5.0, but I am experiencing some troubles. > > > > First, I had to remove > > > > > > > > from [1], since Wicket was complaining that the element had to be > > closed (?): now things are working fine again (as it used to do up to > > 7.4.0), but I honestly do not understand why. > > > > Now I am getting [2] and AFAIU this depends on the fact that the > > WebSocketSettings I am using in [3] have a null or empty 'filterPrefix': > > again, this works perfectly fine with 7.4.0. > > > > Any hint? Thanks. > > Regards. > > > > [1] > > https://github.com/apache/syncope/blob/2_0_X/client/console/src/main/resources/org/apache/syncope/client/console/pages/Login.html#L58-L59 > > [2] https://paste.apache.org/YSzq > > [3] > > https://github.com/apache/syncope/blob/2_0_X/client/console/src/main/java/org/apache/syncope/client/console/pages/BasePage.java#L91 > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems upgrading from 7.4.0 to 7.5.0
On 2016-10-27 11:26 (+0200), Martin Grigorov wrote: > Hi, > > On Thu, Oct 27, 2016 at 10:28 AM, Francesco Chicchiriccò < > ilgro...@apache.org> wrote: > > > Hi all, > > I am trying to upgrade the Apache Syncope console from 7.4.0 to recent > > 7.5.0, but I am experiencing some troubles. > > > > First, I had to remove > > > > > > > > from [1], since Wicket was complaining that the element had to be > > closed (?): now things are working fine again (as it used to do up to > > 7.4.0), but I honestly do not understand why. > > > > What do you mean by "now it works fine" ? > How do you get the i18n-ed value of "submit" now ? This was answered by Sven. > > Now I am getting [2] and AFAIU this depends on the fact that the > > WebSocketSettings I am using in [3] have a null or empty 'filterPrefix': > > again, this works perfectly fine with 7.4.0. > > > > Please file a bug for [2]. It is a regression. Sure: WICKET-6262 Any clever workaround, in the meanwhile? > Most probably [1] is also a bug but I have to try it. Please create a > ticket for it too. Given Sven's reply, I will not create a ticket for this. Thanks for your support. Regards. > > Any hint? Thanks. > > Regards. > > > > [1] https://github.com/apache/syncope/blob/2_0_X/client/ > > console/src/main/resources/org/apache/syncope/client/ > > console/pages/Login.html#L58-L59 > > [2] https://paste.apache.org/YSzq > > [3] https://github.com/apache/syncope/blob/2_0_X/client/ > > console/src/main/java/org/apache/syncope/client/console/ > > pages/BasePage.java#L91 > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems upgrading from 7.4.0 to 7.5.0
On Thu, Oct 27, 2016 at 12:19 PM, Francesco Chicchiriccò < ilgro...@apache.org> wrote: > On 2016-10-27 11:26 (+0200), Martin Grigorov wrote: > > Hi, > > > > On Thu, Oct 27, 2016 at 10:28 AM, Francesco Chicchiriccò < > > ilgro...@apache.org> wrote: > > > > > Hi all, > > > I am trying to upgrade the Apache Syncope console from 7.4.0 to recent > > > 7.5.0, but I am experiencing some troubles. > > > > > > First, I had to remove > > > > > > > > > > > > from [1], since Wicket was complaining that the element had > to be > > > closed (?): now things are working fine again (as it used to do up to > > > 7.4.0), but I honestly do not understand why. > > > > > > > What do you mean by "now it works fine" ? > > How do you get the i18n-ed value of "submit" now ? > > This was answered by Sven. > > > > Now I am getting [2] and AFAIU this depends on the fact that the > > > WebSocketSettings I am using in [3] have a null or empty > 'filterPrefix': > > > again, this works perfectly fine with 7.4.0. > > > > > > > Please file a bug for [2]. It is a regression. > > Sure: WICKET-6262 > Thanks! > > Any clever workaround, in the meanwhile? > The only way I see is to copy/paste the whole #renderHead() and replace Args .notEmpty(filterPrefix, "filterPrefix"); with Args.notNull(filterPrefix, " filterPrefix"); > > > Most probably [1] is also a bug but I have to try it. Please create a > > ticket for it too. > > Given Sven's reply, I will not create a ticket for this. > I'll see whether it is possible to give a better error message > > Thanks for your support. > Regards. > > > > Any hint? Thanks. > > > Regards. > > > > > > [1] https://github.com/apache/syncope/blob/2_0_X/client/ > > > console/src/main/resources/org/apache/syncope/client/ > > > console/pages/Login.html#L58-L59 > > > [2] https://paste.apache.org/YSzq > > > [3] https://github.com/apache/syncope/blob/2_0_X/client/ > > > console/src/main/java/org/apache/syncope/client/console/ > > > pages/BasePage.java#L91 > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Problems upgrading from 7.4.0 to 7.5.0
On 2016-10-27 12:24 (+0200), Martin Grigorov wrote: > On Thu, Oct 27, 2016 at 12:19 PM, Francesco Chicchiriccò < > ilgro...@apache.org> wrote: > > > On 2016-10-27 11:26 (+0200), Martin Grigorov wrote: > > > Hi, > > > > > > On Thu, Oct 27, 2016 at 10:28 AM, Francesco Chicchiriccò > > > wrote: > > > > > > > Hi all, > > > > I am trying to upgrade the Apache Syncope console from 7.4.0 to recent > > > > 7.5.0, but I am experiencing some troubles. > > > > > > > > First, I had to remove > > > > > > > > > > > > > > > > from [1], since Wicket was complaining that the element had > > to be > > > > closed (?): now things are working fine again (as it used to do up to > > > > 7.4.0), but I honestly do not understand why. > > > > > > > > > > What do you mean by "now it works fine" ? > > > How do you get the i18n-ed value of "submit" now ? > > > > This was answered by Sven. > > > > > > Now I am getting [2] and AFAIU this depends on the fact that the > > > > WebSocketSettings I am using in [3] have a null or empty > > 'filterPrefix': > > > > again, this works perfectly fine with 7.4.0. > > > > > > > > > > Please file a bug for [2]. It is a regression. > > > > Sure: WICKET-6262 > > > > Thanks! > > > > > > Any clever workaround, in the meanwhile? > > > > The only way I see is to copy/paste the whole #renderHead() and replace Args > .notEmpty(filterPrefix, "filterPrefix"); with Args.notNull(filterPrefix, " > filterPrefix"); > Unfortunately, BaseWebSocketBehavior#resourceName is private... > > > > > Most probably [1] is also a bug but I have to try it. Please create a > > > ticket for it too. > > > > Given Sven's reply, I will not create a ticket for this. > > > > I'll see whether it is possible to give a better error message > > > > > > Thanks for your support. > > Regards. > > > > > > Any hint? Thanks. > > > > Regards. > > > > > > > > [1] https://github.com/apache/syncope/blob/2_0_X/client/ > > > > console/src/main/resources/org/apache/syncope/client/ > > > > console/pages/Login.html#L58-L59 > > > > [2] https://paste.apache.org/YSzq > > > > [3] https://github.com/apache/syncope/blob/2_0_X/client/ > > > > console/src/main/java/org/apache/syncope/client/console/ > > > > pages/BasePage.java#L91 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
BootstrapPagingNavigator - Wicket-Boostrap 0.10.10 and Wicket 7.5.0
Wicket-Boostrap 0.10.10 and Wicket 7.5.0 When using a BootstrapPagingNavigator, I get this error : Last cause: The component(s) below failed to render. Possible reasons could be that: 1) you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered), 2) if your components were added in a parent container then make sure the markup for the child container includes them in . 1. [Component id = pageNumber] The label with id 'pageNumber' that failed to render was constructed at de.agilecoders.wicket.core.markup.html.bootstrap.navigation.BootstrapPagingNavigator$1.populateItem(BootstrapPagingNavigator.java:106) at org.apache.wicket.Page.onBeforeRender(Page.java:801) at org.apache.wicket.Page.internalPrepareForRender(Page.java:242) at org.apache.wicket.Page.renderPage(Page.java:1018) at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124) at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236) at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175) at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895) at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293) at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:261) With Wicket 7.4.0, all is fine François
Re: how to call modal window on link
Hi thank you for your help but the below lines in OpenWindowOnLoadBehavior seems to be creating issue @Override public void renderHead(IHeaderResponse response) { response.renderOnLoadJavascript(getCallbackScript().toString()); } I followed code in http://stackoverflow.com/questions/4765790/how-to-open-modaldialog-on-pageload. I cant get it working :(. Please advise. Thank you. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-call-modal-window-on-link-tp4675882p4675903.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: BootstrapPagingNavigator - Wicket-Boostrap 0.10.10 and Wicket 7.5.0
Same here. On 2016-10-27 13:10 (+0200), Francois Meillet wrote: > Wicket-Boostrap 0.10.10 and Wicket 7.5.0 > When using a BootstrapPagingNavigator, I get this error : > > > Last cause: The component(s) below failed to render. Possible reasons could > be that: 1) you have added a component in code but forgot to reference it in > the markup (thus the component will never be rendered), 2) if your components > were added in a parent container then make sure the markup for the child > container includes them in . > > 1. [Component id = pageNumber] > The label with id 'pageNumber' that failed to render was constructed > at > de.agilecoders.wicket.core.markup.html.bootstrap.navigation.BootstrapPagingNavigator$1.populateItem(BootstrapPagingNavigator.java:106) > at org.apache.wicket.Page.onBeforeRender(Page.java:801) > at org.apache.wicket.Page.internalPrepareForRender(Page.java:242) > at org.apache.wicket.Page.renderPage(Page.java:1018) > at > org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124) > at > org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236) > at > org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175) > at > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895) > at > org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) > at > org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265) > at > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222) > at > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293) > at > org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:261) > > With Wicket 7.4.0, all is fine > > François - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: how to call modal window on link
On Thu, Oct 27, 2016 at 1:41 PM, Pratibha wrote: > Hi thank you for your help but the below lines in OpenWindowOnLoadBehavior > seems to be creating issue > What kind of issue ? > > @Override > public void renderHead(IHeaderResponse response) { > response.renderOnLoadJavascript(getCallbackScript().toString()); > } > > I followed code in > http://stackoverflow.com/questions/4765790/how-to-open- > modaldialog-on-pageload. > > I cant get it working :(. Please advise. > > Thank you. > > > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/how-to-call-modal-window-on-link-tp4675882p4675903.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: how to call modal window on link
Compile error..The method renderOnLoadJavascript(String) is undefined for the type IHeaderResponse public class OpenWindowOnLoadBehavior extends AbstractDefaultAjaxBehavior { @Override protected void respond(AjaxRequestTarget target) { ModalWindow window = (ModalWindow) getComponent(); window.show(target); } @Override public void renderHead(final Component component, IHeaderResponse response) { //*response.renderOnLoadJavascript(getCallbackScript().toString());* } } -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-call-modal-window-on-link-tp4675882p4675906.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: how to call modal window on link
I am trying to call modal window but this is not working my code is @Override public void onClick() { confirmModal.add(new OpenWindowOnLoadBehavior()); confirmModal.setPageCreator(new ModalWindow.PageCreator() { @Override public Page createPage() { return new RedirectPage("http://www.google.com";); } }); } public class OpenWindowOnLoadBehavior extends AbstractDefaultAjaxBehavior { @Override protected void respond(AjaxRequestTarget target) { ModalWindow window = (ModalWindow) getComponent(); window.show(target); } @Override public void renderHead(final Component component, IHeaderResponse response) { *response.renderOnLoadJavascript(getCallbackScript().toString());* } Please help me with this. Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-call-modal-window-on-link-tp4675882p4675907.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
Hi, Good news! It is a bug in Wicket Bootstrap: https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/core/markup/html/bootstrap/dialog/Alert.html#L10 This uses a Label in Java. (No idea why). Since https://issues.apache.org/jira/browse/WICKET-6219 this is not possible. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Oct 27, 2016 at 1:10 PM, Joachim Rohde wrote: > We are having a custom FeedbackPanel which extends from NotificationPanel. > After upgrading from Wicket 7.4.0 to 7.5.0 an > unexpected runtime exception is thrown as soon as an error message should > be rendered (see below). > > I have created a quickstart with a simple link which demonstrates this > behavior. With Wicket 7.4.0 everything works as > expected. With Wicket 7.5.0 you'll get an exception. > > When using the Wicket FeedbackPanel everything works fine. I have no clue > if this is a bug in Wicket itself or Wicket > Bootstrap. Any help is appreciated. > > Joachim > > > The generated exception: > > Unexpected RuntimeException > > Last cause: The component(s) below failed to render. Possible reasons > could be that: 1) you have added a component in > code but forgot to reference it in the markup (thus the component will > never be rendered), 2) if your components were > added in a parent container then make sure the markup for the child > container includes them in . > > 1. [Component id = message] > > Stacktrace > > Root cause: > > org.apache.wicket.WicketRuntimeException: The component(s) below failed > to render. Possible reasons could be that: 1) > you have added a component in code but forgot to reference it in the > markup (thus the component will never be rendered), > 2) if your components were added in a parent container then make sure the > markup for the child container includes them > in . > > 1. [Component id = message] > > at org.apache.wicket.Page.checkRendering(Page.java:666) > at org.apache.wicket.Page.endComponentRender(Page.java:317) > at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent( > XmlPartialPageUpdate.java:127) > at org.apache.wicket.page.PartialPageUpdate.writeComponents( > PartialPageUpdate.java:248) > at org.apache.wicket.page.PartialPageUpdate.writeTo( > PartialPageUpdate.java:161) > at org.apache.wicket.ajax.AjaxRequestHandler.respond( > AjaxRequestHandler.java:358) > at org.apache.wicket.request.cycle.RequestCycle$ > HandlerExecutor.respond(RequestCycle.java:895) > at org.apache.wicket.request.RequestHandlerStack.execute( > RequestHandlerStack.java:64) > at org.apache.wicket.request.RequestHandlerStack.execute( > RequestHandlerStack.java:97) > at org.apache.wicket.request.cycle.RequestCycle.execute( > RequestCycle.java:265) > at org.apache.wicket.request.cycle.RequestCycle. > processRequest(RequestCycle.java:222) > at org.apache.wicket.request.cycle.RequestCycle. > processRequestAndDetach(RequestCycle.java:293) > at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle( > WicketFilter.java:261) > at org.apache.wicket.protocol.http.WicketFilter. > processRequest(WicketFilter.java:203) > at org.apache.wicket.protocol.http.WicketFilter.doFilter( > WicketFilter.java:284) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( > ApplicationFilterChain.java:239) > at org.apache.catalina.core.ApplicationFilterChain.doFilter( > ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke( > StandardWrapperValve.java:217) > at org.apache.catalina.core.StandardContextValve.invoke( > StandardContextValve.java:106) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke( > AuthenticatorBase.java:502) > at org.apache.catalina.core.StandardHostValve.invoke( > StandardHostValve.java:142) > at org.apache.catalina.valves.ErrorReportValve.invoke( > ErrorReportValve.java:79) > at org.apache.catalina.valves.AbstractAccessLogValve.invoke( > AbstractAccessLogValve.java:616) > at org.apache.catalina.core.StandardEngineValve.invoke( > StandardEngineValve.java:88) > at org.apache.catalina.connector.CoyoteAdapter.service( > CoyoteAdapter.java:518) > at org.apache.coyote.http11.AbstractHttp11Processor.process( > AbstractHttp11Processor.java:1091) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler. > process(AbstractProtocol.java:673) > at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. > doRun(NioEndpoint.java:1500) > at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. > run(NioEndpoint.java:1456) > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run( > TaskThread.java:61) > at j
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
https://github.com/l0rdn1kk0n/wicket-bootstrap/issues/642 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Oct 27, 2016 at 2:18 PM, Martin Grigorov wrote: > Hi, > > Good news! > It is a bug in Wicket Bootstrap: https://github.com/ > l0rdn1kk0n/wicket-bootstrap/blob/wicket-7.x/bootstrap- > core/src/main/java/de/agilecoders/wicket/core/ > markup/html/bootstrap/dialog/Alert.html#L10 > This uses a Label in Java. (No idea why). > Since https://issues.apache.org/jira/browse/WICKET-6219 this is not > possible. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Oct 27, 2016 at 1:10 PM, Joachim Rohde wrote: > >> We are having a custom FeedbackPanel which extends from >> NotificationPanel. After upgrading from Wicket 7.4.0 to 7.5.0 an >> unexpected runtime exception is thrown as soon as an error message should >> be rendered (see below). >> >> I have created a quickstart with a simple link which demonstrates this >> behavior. With Wicket 7.4.0 everything works as >> expected. With Wicket 7.5.0 you'll get an exception. >> >> When using the Wicket FeedbackPanel everything works fine. I have no clue >> if this is a bug in Wicket itself or Wicket >> Bootstrap. Any help is appreciated. >> >> Joachim >> >> >> The generated exception: >> >> Unexpected RuntimeException >> >> Last cause: The component(s) below failed to render. Possible reasons >> could be that: 1) you have added a component in >> code but forgot to reference it in the markup (thus the component will >> never be rendered), 2) if your components were >> added in a parent container then make sure the markup for the child >> container includes them in . >> >> 1. [Component id = message] >> >> Stacktrace >> >> Root cause: >> >> org.apache.wicket.WicketRuntimeException: The component(s) below failed >> to render. Possible reasons could be that: 1) >> you have added a component in code but forgot to reference it in the >> markup (thus the component will never be rendered), >> 2) if your components were added in a parent container then make sure the >> markup for the child container includes them >> in . >> >> 1. [Component id = message] >> >> at org.apache.wicket.Page.checkRendering(Page.java:666) >> at org.apache.wicket.Page.endComponentRender(Page.java:317) >> at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(X >> mlPartialPageUpdate.java:127) >> at org.apache.wicket.page.PartialPageUpdate.writeComponents(Par >> tialPageUpdate.java:248) >> at org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPage >> Update.java:161) >> at org.apache.wicket.ajax.AjaxRequestHandler.respond(AjaxReques >> tHandler.java:358) >> at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor >> .respond(RequestCycle.java:895) >> at org.apache.wicket.request.RequestHandlerStack.execute(Reques >> tHandlerStack.java:64) >> at org.apache.wicket.request.RequestHandlerStack.execute(Reques >> tHandlerStack.java:97) >> at org.apache.wicket.request.cycle.RequestCycle.execute(Request >> Cycle.java:265) >> at org.apache.wicket.request.cycle.RequestCycle.processRequest( >> RequestCycle.java:222) >> at org.apache.wicket.request.cycle.RequestCycle.processRequestA >> ndDetach(RequestCycle.java:293) >> at org.apache.wicket.protocol.http.WicketFilter.processRequestC >> ycle(WicketFilter.java:261) >> at org.apache.wicket.protocol.http.WicketFilter.processRequest( >> WicketFilter.java:203) >> at org.apache.wicket.protocol.http.WicketFilter.doFilter(Wicket >> Filter.java:284) >> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi >> lter(ApplicationFilterChain.java:239) >> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App >> licationFilterChain.java:206) >> at org.apache.catalina.core.StandardWrapperValve.invoke(Standar >> dWrapperValve.java:217) >> at org.apache.catalina.core.StandardContextValve.invoke(Standar >> dContextValve.java:106) >> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(A >> uthenticatorBase.java:502) >> at org.apache.catalina.core.StandardHostValve.invoke(StandardHo >> stValve.java:142) >> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo >> rtValve.java:79) >> at org.apache.catalina.valves.AbstractAccessLogValve.invoke(Abs >> tractAccessLogValve.java:616) >> at org.apache.catalina.core.StandardEngineValve.invoke(Standard >> EngineValve.java:88) >> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd >> apter.java:518) >> at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs >> tractHttp11Processor.java:1091) >> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler >> .process(AbstractProtocol.java:673) >> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun >> (NioEndpoint.java:1500) >> at org.apache.tomcat.util.net.NioEndpoint$SocketProcess
Re: BootstrapPagingNavigator - Wicket-Boostrap 0.10.10 and Wicket 7.5.0
https://github.com/l0rdn1kk0n/wicket-bootstrap/issues/642 Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Oct 27, 2016 at 1:10 PM, Francois Meillet < francois.meil...@gmail.com> wrote: > Wicket-Boostrap 0.10.10 and Wicket 7.5.0 > When using a BootstrapPagingNavigator, I get this error : > > > Last cause: The component(s) below failed to render. Possible reasons > could be that: 1) you have added a component in code but forgot to > reference it in the markup (thus the component will never be rendered), 2) > if your components were added in a parent container then make sure the > markup for the child container includes them in . > > 1. [Component id = pageNumber] > The label with id 'pageNumber' that failed to render was constructed > at de.agilecoders.wicket.core.markup.html.bootstrap.navigation. > BootstrapPagingNavigator$1.populateItem(BootstrapPagingNavigator.java:106) > at org.apache.wicket.Page.onBeforeRender(Page.java:801) > at org.apache.wicket.Page.internalPrepareForRender(Page.java:242) > at org.apache.wicket.Page.renderPage(Page.java:1018) > at org.apache.wicket.request.handler.render. > WebPageRenderer.renderPage(WebPageRenderer.java:124) > at org.apache.wicket.request.handler.render.WebPageRenderer.respond( > WebPageRenderer.java:236) > at org.apache.wicket.core.request.handler.RenderPageRequestHandler. > respond(RenderPageRequestHandler.java:175) > at org.apache.wicket.request.cycle.RequestCycle$ > HandlerExecutor.respond(RequestCycle.java:895) > at org.apache.wicket.request.RequestHandlerStack.execute( > RequestHandlerStack.java:64) > at org.apache.wicket.request.cycle.RequestCycle.execute( > RequestCycle.java:265) > at org.apache.wicket.request.cycle.RequestCycle. > processRequest(RequestCycle.java:222) > at org.apache.wicket.request.cycle.RequestCycle. > processRequestAndDetach(RequestCycle.java:293) > at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle( > WicketFilter.java:261) > > With Wicket 7.4.0, all is fine > > François
Re: how to call modal window on link
response.render(OnLoadHeaderItem.forScript(getCallbackScript().toString()); Should be something like this. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Oct 27, 2016 at 2:08 PM, Pratibha wrote: > I am trying to call modal window but this is not working my code is > > @Override > public void onClick() { > > confirmModal.add(new > OpenWindowOnLoadBehavior()); > confirmModal.setPageCreator(new > ModalWindow.PageCreator() { > @Override > public Page createPage() { > return new RedirectPage("http://www.google.com";); > } > }); > } > > public class OpenWindowOnLoadBehavior extends AbstractDefaultAjaxBehavior { > @Override > protected void respond(AjaxRequestTarget target) { > ModalWindow window = (ModalWindow) getComponent(); > window.show(target); > } > @Override > public void renderHead(final Component component, IHeaderResponse > response) { > > *response.renderOnLoadJavascript(getCallbackScript().toString());* > } > > Please help me with this. > > Thanks > > > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/how-to-call-modal-window-on-link-tp4675882p4675907.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
Great. Thanks for the fast reply Martin. Do you have already a clue when a new version of Wicket Bootstrap will be released? On 10/27/2016 02:18 PM, Martin Grigorov wrote: > Hi, > > Good news! > It is a bug in Wicket Bootstrap: > https://github.com/l0rdn1kk0n/wicket-bootstrap/blob/wicket-7.x/bootstrap-core/src/main/java/de/agilecoders/wicket/core/markup/html/bootstrap/dialog/Alert.html#L10 > > This uses a Label in Java. (No idea why). > Since https://issues.apache.org/jira/browse/WICKET-6219 this is not > possible. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Oct 27, 2016 at 1:10 PM, Joachim Rohde wrote: > >> We are having a custom FeedbackPanel which extends from NotificationPanel. >> After upgrading from Wicket 7.4.0 to 7.5.0 an >> unexpected runtime exception is thrown as soon as an error message should >> be rendered (see below). >> >> I have created a quickstart with a simple link which demonstrates this >> behavior. With Wicket 7.4.0 everything works as >> expected. With Wicket 7.5.0 you'll get an exception. >> >> When using the Wicket FeedbackPanel everything works fine. I have no clue >> if this is a bug in Wicket itself or Wicket >> Bootstrap. Any help is appreciated. >> >> Joachim >> >> >> The generated exception: >> >> Unexpected RuntimeException >> >> Last cause: The component(s) below failed to render. Possible reasons >> could be that: 1) you have added a component in >> code but forgot to reference it in the markup (thus the component will >> never be rendered), 2) if your components were >> added in a parent container then make sure the markup for the child >> container includes them in . >> >> 1. [Component id = message] >> >> Stacktrace >> >> Root cause: >> >> org.apache.wicket.WicketRuntimeException: The component(s) below failed >> to render. Possible reasons could be that: 1) >> you have added a component in code but forgot to reference it in the >> markup (thus the component will never be rendered), >> 2) if your components were added in a parent container then make sure the >> markup for the child container includes them >> in . >> >> 1. [Component id = message] >> >> at org.apache.wicket.Page.checkRendering(Page.java:666) >> at org.apache.wicket.Page.endComponentRender(Page.java:317) >> at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent( >> XmlPartialPageUpdate.java:127) >> at org.apache.wicket.page.PartialPageUpdate.writeComponents( >> PartialPageUpdate.java:248) >> at org.apache.wicket.page.PartialPageUpdate.writeTo( >> PartialPageUpdate.java:161) >> at org.apache.wicket.ajax.AjaxRequestHandler.respond( >> AjaxRequestHandler.java:358) >> at org.apache.wicket.request.cycle.RequestCycle$ >> HandlerExecutor.respond(RequestCycle.java:895) >> at org.apache.wicket.request.RequestHandlerStack.execute( >> RequestHandlerStack.java:64) >> at org.apache.wicket.request.RequestHandlerStack.execute( >> RequestHandlerStack.java:97) >> at org.apache.wicket.request.cycle.RequestCycle.execute( >> RequestCycle.java:265) >> at org.apache.wicket.request.cycle.RequestCycle. >> processRequest(RequestCycle.java:222) >> at org.apache.wicket.request.cycle.RequestCycle. >> processRequestAndDetach(RequestCycle.java:293) >> at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle( >> WicketFilter.java:261) >> at org.apache.wicket.protocol.http.WicketFilter. >> processRequest(WicketFilter.java:203) >> at org.apache.wicket.protocol.http.WicketFilter.doFilter( >> WicketFilter.java:284) >> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( >> ApplicationFilterChain.java:239) >> at org.apache.catalina.core.ApplicationFilterChain.doFilter( >> ApplicationFilterChain.java:206) >> at org.apache.catalina.core.StandardWrapperValve.invoke( >> StandardWrapperValve.java:217) >> at org.apache.catalina.core.StandardContextValve.invoke( >> StandardContextValve.java:106) >> at org.apache.catalina.authenticator.AuthenticatorBase.invoke( >> AuthenticatorBase.java:502) >> at org.apache.catalina.core.StandardHostValve.invoke( >> StandardHostValve.java:142) >> at org.apache.catalina.valves.ErrorReportValve.invoke( >> ErrorReportValve.java:79) >> at org.apache.catalina.valves.AbstractAccessLogValve.invoke( >> AbstractAccessLogValve.java:616) >> at org.apache.catalina.core.StandardEngineValve.invoke( >> StandardEngineValve.java:88) >> at org.apache.catalina.connector.CoyoteAdapter.service( >> CoyoteAdapter.java:518) >> at org.apache.coyote.http11.AbstractHttp11Processor.process( >> AbstractHttp11Processor.java:1091) >> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler. >> process(AbstractProtocol.java:673) >> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. >> doRun(NioEndpoint.java:1500) >> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor. >> run(NioEndpoint
Re: how to call modal window on link
Thank you that seems to be working but when i click on link it first opens the same page in new tab and after that i can see modalWindow. So basically i end up with 2 same pages in 2 tabs one with modalwindow. confirmModal.add(new OpenWindowOnLoadBehavior()); confirmModal.setContent(new ComplaintModal(confirmModal.getContentId(),confirmModal,_form)); I need modalwindow to be opened in same page on button click. Thank you so much... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/how-to-call-modal-window-on-link-tp4675882p4675913.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
On 2016-10-27 14:40 (+0200), Joachim Rohde wrote: > Great. Thanks for the fast reply Martin. Do you have already a clue when a > new version of Wicket Bootstrap will be released? ..or an easy way to backport your fix? Regards. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
The release script is running... Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò wrote: > > > On 2016-10-27 14:40 (+0200), Joachim Rohde wrote: > > Great. Thanks for the fast reply Martin. Do you have already a clue when > a new version of Wicket Bootstrap will be released? > > ..or an easy way to backport your fix? > > Regards. > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
0.10.11 should be at Maven Central any time soon! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Oct 27, 2016 at 3:06 PM, Martin Grigorov wrote: > The release script is running... > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò < > ilgro...@apache.org> wrote: > >> >> >> On 2016-10-27 14:40 (+0200), Joachim Rohde wrote: >> > Great. Thanks for the fast reply Martin. Do you have already a clue >> when a new version of Wicket Bootstrap will be released? >> >> ..or an easy way to backport your fix? >> >> Regards. >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
super ! François > Le 27 oct. 2016 à 15:17, Martin Grigorov a écrit : > > 0.10.11 should be at Maven Central any time soon! > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Oct 27, 2016 at 3:06 PM, Martin Grigorov > wrote: > >> The release script is running... >> >> Martin Grigorov >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò < >> ilgro...@apache.org> wrote: >> >>> >>> >>> On 2016-10-27 14:40 (+0200), Joachim Rohde wrote: Great. Thanks for the fast reply Martin. Do you have already a clue >>> when a new version of Wicket Bootstrap will be released? >>> >>> ..or an easy way to backport your fix? >>> >>> Regards. >>> >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with Wicket 7.5.0 and Wicket Bootstrap 0.10.10 using a custom NotificationPanel
Wow. Thanks a lot. On 10/27/2016 03:17 PM, Martin Grigorov wrote: > 0.10.11 should be at Maven Central any time soon! > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Oct 27, 2016 at 3:06 PM, Martin Grigorov > wrote: > >> The release script is running... >> >> Martin Grigorov >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Thu, Oct 27, 2016 at 3:03 PM, Francesco Chicchiriccò < >> ilgro...@apache.org> wrote: >> >>> >>> >>> On 2016-10-27 14:40 (+0200), Joachim Rohde wrote: Great. Thanks for the fast reply Martin. Do you have already a clue >>> when a new version of Wicket Bootstrap will be released? >>> >>> ..or an easy way to backport your fix? >>> >>> Regards. >>> >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> > -- SOLVIT GmbH Joachim Rohde Softwareentwicklung Lise-Meitner-Straße 4 24941 Flensburg Telefon: +49 461 57 49 85 94 Fax: +49 461 57 49 88 99 Geschäftsführung: Benjamin Klink, Karsten Paulsen, Helge Werlein Amtsgericht Flensburg HRB 9450 FL St.-Nr.: 15/296/14057 - USt-Id.: DE 283 368 011 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
AutocompleteTextField on submit : The value of .. is not a valid ...
Hi, Please help me with following issue: I'm using wicket 7. I have a form with a AutocompleteTextField. The autocompletion works ok until I need to submit the form, when I get following message: - The value of 'test' is not a valid TestBean. Here is my component: IAutoCompleteRenderer testRenderer = new IAutoCompleteRenderer() { private static final long serialVersionUID = -7038764178796856779L; @Override public void render(TestBean object, Response response, String criteria) { response.write((new StringBuilder()).append("").toString()); response.write(object.getUniqueName()); response.write(""); } @Override public void renderFooter(Response response, int ItemId) { response.write(""); } @Override public void renderHeader(Response response) { response.write(""); } }; AutoCompleteTextField txt = new AutoCompleteTextField("test", new PropertyModel(this, "myTestBean"), TestBean.class, testRenderer, (new AutoCompleteSettings().setPreselect(true))) { private static final long serialVersionUID = 1L; private List TestList = null; @Override protected Iterator getChoices(String input) { if (Strings.isEmpty(input)) { return Collections.emptyIterator(); } else { if (input.length() > 0) { if (TestList == null || TestList.isEmpty() || !input.substring(0, 1).toUpperCase().equals(TestList.get(0).getUniqueName().substring(0, 1).toUpperCase())) { TestList = SpringCtx.getAppDB(TestBeanDao.class).selectAproxByUniqueName(input.substring(0, 1)); } } } int autoCompleteFieldNumChoices = 20; List choices = new ArrayList(autoCompleteFieldNumChoices); for (int i = 0; i < TestList.size(); i++) { final TestBean testBean = TestList.get(i); final String testName = testBean.getUniqueName(); if (testName.toUpperCase().startsWith(input.toUpperCase())) { choices.add(testBean); if (choices.size() == autoCompleteFieldNumChoices) { break; } } } return choices.iterator(); } };
Re: how to call modal window on link
checked that you don't target="_blank" on that link. On Thu, Oct 27, 2016 at 2:40 PM, Pratibha wrote: > Thank you that seems to be working but when i click on link it first opens > the same page in new tab and after that i can see modalWindow. > > So basically i end up with 2 same pages in 2 tabs one with modalwindow. > > confirmModal.add(new OpenWindowOnLoadBehavior()); > confirmModal.setContent(new > ComplaintModal(confirmModal.getContentId(),confirmModal,_form)); > > I need modalwindow to be opened in same page on button click. > > Thank you so much... > > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/how-to-call-modal-window-on-link-tp4675882p4675913.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
Re: 8.0.0-M1 MarkupNotFoundException
Hi Martin, Ok, thanks. The quickstart was stripped down to a bare minimum of html that would demonstrate the issue. So yes, in the real application the tags surround elements and the Page is inherited from a Bootstrap template with , etc. Issue is now fixed thanks to Andrea. Thanks again, Regards, Greg -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/8-0-0-M1-wicket-link-MarkupNotFoundException-tp4675812p4675921.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 8.0.0-M1 MarkupNotFoundException
should be ... > So yes, in the real application the > > tags surround \ > < > a\ > > > elements and the Page is inherited from a -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/8-0-0-M1-wicket-link-MarkupNotFoundException-tp4675812p4675922.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org