Re: RestartResponseException within Modal window

[Jorge Fernandez]

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 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,
>>
>> 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 ideas on how this can be achieved?
>>
>> Thanks
>>
>>
>

Re: RestartResponseException within Modal window

[Sven Meier]

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,

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 ideas on how this can be achieved?

Thanks

RestartResponseException within Modal window

[Jorge Fernandez]

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 ideas on how this can be achieved?

Thanks

Re: Disable component to prevent double click

[Andrea Del Bene]

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.
Id you are not using AJAX you can not use this behavior and you must
provide the JavaScript code in some other way. For example with SubmitLink
you have to override getTriggerJavaScript. Unfortunately "disabling" a html
component is not a standard procedure so for those components that don't
support the attribute 'disabled' we must use custom JavaScript.

On Mon, Feb 19, 2018 at 9:55 PM, Claudia Hirt  wrote:

> By the way: is there any reason why AjaxDisableComponentListener has no
> public constructor?
>
> > Am 19.02.2018 um 21:49 schrieb Claudia Hirt :
> >
> > Hi all,
> > I‘m facing the problem of double submits when double clicking on buttons
> and links. I was very pleased to see there’s a new listener of
> https://issues.apache.org/jira/browse/WICKET-6448 implemented in wicket
> 7.10. But this only works for Buttons not for links like a SubmitLink. I‘m
> also facing the same issue for non-ajax-components.
> > Any suggestions how to solve this?
> > Thanks in advance!
> > Best regards, Claudia
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

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

[Rich Bowen]

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 community.


We’ll have four tracks of technical content this time, as well as lots 
of opportunities to connect with your project community, hack on the 
code, and learn about other related (and unrelated!) projects across the 
foundation.


The Call For Papers (CFP) [2] and registration are now open. Register 
early to take advantage of the early bird prices and secure your place 
at the event hotel.


Important dates
March 30: CFP closes
April 20: CFP notifications sent
	August 24: Hotel room block closes (please do not wait until the last 
minute)


Follow @ApacheCon on Twitter to be the first to hear announcements about 
keynotes, the schedule, evening events, and everything you can expect to 
see at the event.


See you in Montréal!

Sincerely, Rich Bowen, V.P. Events,
on behalf of the entire ApacheCon team

[1] http://www.apachecon.com/acna18
[2] https://cfp.apachecon.com/conference.html?apachecon-north-america-2018

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

[ANNOUNCE] WicketStuff 7.10.0 Released

[Maxim Solodovnik]

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 (4):
  Merge pull request #620 from rene-d-menoto/debug-log-widgets
  White-spaces are fixed
  Tests are fixed
  Wicketstuff 7.10.0 is released

The WicketStuff team

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Issues upgrading to Wicket 8.0.0-M9

[Sebastien Briquet]

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 WicketEventJQueryResourceReference. It would be
> great
> > if someone could cut a milestone release for WiQuery as well, so I can do
> > further testing with my application.
>
> I've just pushed a fix for this. WiQuery master now compiles against M9.
> Please
> not that wiquery-jquery-ui is hopelessly outdated. I hope to get that
> fixed in
> the comming month. However, it seems jquery-ui is dead as well (which does
> make it easier to stay up to date from now on :) ).
>
> Best regards,
> Emond
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: Issues upgrading to Wicket 8.0.0-M9

[Emond Papegaaij]

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 application.

I've just pushed a fix for this. WiQuery master now compiles against M9. Please 
not that wiquery-jquery-ui is hopelessly outdated. I hope to get that fixed in 
the comming month. However, it seems jquery-ui is dead as well (which does 
make it easier to stay up to date from now on :) ).

Best regards,
Emond



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org