Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-23 Thread Petr Zajac
. On Thu, May 23, 2013 at 12:39 AM, Petr Zajac petr.za...@gmail.com wrote: Hi Martin, thanks for the quick answer. Yes, the text fields are not empty and the parameters in requests are also empty. I found why after small investigation. The text fields are disabled after pressing submit button by using

Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-23 Thread Petr Zajac
on this button. Depending on which one is executed first the data will be send or not. By moving this logic in onAfter() handler you can be sure that the data is already sent when you disable the fields. On Thu, May 23, 2013 at 1:58 PM, Petr Zajac petr.za...@gmail.com wrote: Hi, the JS is registered

Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-22 Thread Petr Zajac
Hi, when I tried to upgrade to to Wicket 6.8.0 I found probably serious issue. We have Form with two text fields ('username' and 'password'). We set CompoundPropertyModel and bound properties to two textfields. The submit button uses AjaxSubmitLink. When I click to submit button the the form

Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-22 Thread Petr Zajac
, On Wed, May 22, 2013 at 11:07 PM, Petr Zajac petr.za...@gmail.com wrote: Hi, when I tried to upgrade to to Wicket 6.8.0 I found probably serious issue. We have Form with two text fields ('username' and 'password'). We set CompoundPropertyModel and bound properties to two textfields. The submit