Re: RestartResponseException within Modal window

Yes, I need to be able to use RestartResponse since it is used by the application to perform special cleanup/handling. On Tue, Feb 20, 2018 at 3:03 PM, Sven Meier wrote: > Hi, > > do you really need to use a RestartResponseException? > > You could close the dialog and redirect

Re: RestartResponseException within Modal window

Hi, do you really need to use a RestartResponseException? You could close the dialog and redirect afterwards instead:     dialog.close(target);     target.appendJavaScript(|"window.location ='http://www.yoururl.com';");| Have fun Sven Am 20.02.2018 um 18:42 schrieb Jorge Fernandez: Hi,

RestartResponseException within Modal window

Hi, I am trying to handle a RestartResponseException within a Modal window in my application. I would like to be redirected without the UnloadConfirmation. I prefer not to use showUnloadConfirmation(boolean) because I only want to bypass it in this specific case and enable it for others. Any

Re: Disable component to prevent double click

Hi, as reported in its javadoc AjaxDisableComponentListener by default uses the DOM attribute 'disabled' to do its job, but this attribute doesn't work with links. For this kind of components you have to provide the right JavaScript to enable/disable them by overriding generateHandlerJavaScript.

Save the date: ApacheCon North America, September 24-27 in Montréal

Dear Apache Enthusiast, (You’re receiving this message because you’re subscribed to a user@ or dev@ list of one or more Apache Software Foundation projects.) We’re pleased to announce the upcoming ApacheCon [1] in Montréal, September 24-27. This event is all about you — the Apache project

[ANNOUNCE] WicketStuff 7.10.0 Released

WicketStuff core 7.10.0 based on Apache Wicket 7.10.0 is released and soon will be available at Maven Central! The changelog since 7.9.0 is: Andrea Del Bene (2): PR 612 update dependency to 7.10 snapshot. Removed default error code setting in handleException Maxim Solodovnik

Re: Issues upgrading to Wicket 8.0.0-M9

Right, latest jQuery-ui release is September 14, 2016 :( On Tue, Feb 20, 2018 at 1:04 PM, Emond Papegaaij wrote: > On maandag 19 februari 2018 11:22:30 CET Thomas Heigl wrote: > > 1. Current WiQuery version is not compatible with M9 > > > > It still depends on

Re: Issues upgrading to Wicket 8.0.0-M9

On maandag 19 februari 2018 11:22:30 CET Thomas Heigl wrote: > 1. Current WiQuery version is not compatible with M9 > > It still depends on WicketEventJQueryResourceReference. It would be great > if someone could cut a milestone release for WiQuery as well, so I can do > further testing with my