Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-23 Thread Petr Zajac
Hi, after fighting with registration AjaxCallListener to AjaxSubmitLink it works fine now. :-) Thanks Petr Dne 23.5.2013 13:13, Martin Grigorov napsal(a): Hi, Just re-read your previous message. I see now: $submitBtn.click(function(e) {... So you have two listeners on 'click' event on this

Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-23 Thread Martin Grigorov
Hi, Just re-read your previous message. I see now: $submitBtn.click(function(e) {... So you have two listeners on 'click' event 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

Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-23 Thread Petr Zajac
Hi, the JS is registered in @Override public void renderHead(IHeaderResponse response) { ClientSettings settings = new ClientSettings(getMarkupId()); response.render(OnDomReadyHeaderItem.forScript("new IJC.LoginForm(" + settings.toJson() + ");")); } of panel with the

Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-23 Thread Martin Grigorov
Hi Petr, How do you register this JS execution ? You should do it in AjaxCallListener#afterHandler because if you do it earlier then form submit wont sent the values for disabled fields. On Thu, May 23, 2013 at 12:39 AM, Petr Zajac wrote: > Hi Martin, > thanks for the quick answer. Yes, the te

Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-22 Thread Petr Zajac
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 jquery in our code: $form.find('input[type="text"]').add($form.fi

Re: Issue in 6.8.0 - Form with CompoundPropertyModel and AjaxSubmitLink

2013-05-22 Thread Martin Grigorov
Hi, On Wed, May 22, 2013 at 11:07 PM, Petr Zajac 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 button

Re: Issue in 6.8.0

2013-05-21 Thread Maxim Solodovnik
e its private static class FormValidateVisitor, and because > it > > > uses static method to do its main job there is no way to override > > > #updateAjaxAttributes(). > > > But I think this issue is not that big to release 6.8.1. > > > > > > > > > > > &

Re: Issue in 6.8.0

2013-05-21 Thread Martin Grigorov
hank you, > > > Paul Bors > > > > > > -Original Message- > > > From: Maxim Solodovnik [mailto:solomax...@gmail.com] > > > Sent: Tuesday, May 21, 2013 3:39 AM > > > To: users@wicket.apache.org > > > Subject: Re: Issue in 6.

RE: Issue in 6.8.0

2013-05-21 Thread Paul Bors
patch for WICKET-5194 and help the team release 6.8.1 for you guys? ~ Thank you, Paul Bors -Original Message- From: Maxim Solodovnik [mailto:solomax...@gmail.com] Sent: Tuesday, May 21, 2013 10:53 AM To: users@wicket.apache.org Subject: Re: Issue in 6.8.0 What date 6.9.0 is schedule

RE: Issue in 6.8.0

2013-05-21 Thread Paul Bors
To: users@wicket.apache.org Subject: Re: Issue in 6.8.0 On Tue, May 21, 2013 at 5:36 PM, Paul Bors wrote: > WICKET-5194 does not have fix version yet, does that mean is not a > show stopper for the release of 6.8.0? > 6.8.0 is already released. This ticket cannot stop it :-) If the

Re: Issue in 6.8.0

2013-05-21 Thread Maxim Solodovnik
u, > > Paul Bors > > > > -Original Message- > > From: Maxim Solodovnik [mailto:solomax...@gmail.com] > > Sent: Tuesday, May 21, 2013 3:39 AM > > To: users@wicket.apache.org > > Subject: Re: Issue in 6.8.0 > > > > Done > > https://issues.ap

Re: Issue in 6.8.0

2013-05-21 Thread Martin Grigorov
t I think this issue is not that big to release 6.8.1. > > ~ Thank you, > Paul Bors > > -Original Message- > From: Maxim Solodovnik [mailto:solomax...@gmail.com] > Sent: Tuesday, May 21, 2013 3:39 AM > To: users@wicket.apache.org > Subject: Re: Issue in 6.8.0

RE: Issue in 6.8.0

2013-05-21 Thread Paul Bors
WICKET-5194 does not have fix version yet, does that mean is not a show stopper for the release of 6.8.0? ~ Thank you, Paul Bors -Original Message- From: Maxim Solodovnik [mailto:solomax...@gmail.com] Sent: Tuesday, May 21, 2013 3:39 AM To: users@wicket.apache.org Subject: Re: Issue

Re: Issue in 6.8.0

2013-05-21 Thread Maxim Solodovnik
Done https://issues.apache.org/jira/browse/WICKET-5194 On Tue, May 21, 2013 at 2:09 PM, Sven Meier wrote: > Hi Maxim, > > the case is clear, no need for a quickstart. > > Sven > > > > On 05/21/2013 08:59 AM, Maxim Solodovnik wrote: > >> Martin, >> >> Thanks for the quick reply! >> I see no othe

Re: Issue in 6.8.0

2013-05-21 Thread Sven Meier
Hi Maxim, the case is clear, no need for a quickstart. Sven On 05/21/2013 08:59 AM, Maxim Solodovnik wrote: Martin, Thanks for the quick reply! I see no other way than copy paste AjaxFormValidatingBehavior, so I'll file JIRA issue. Is it OK if will create it without quickstart? On Tue, Ma

Re: Issue in 6.8.0

2013-05-20 Thread Maxim Solodovnik
Martin, Thanks for the quick reply! I see no other way than copy paste AjaxFormValidatingBehavior, so I'll file JIRA issue. Is it OK if will create it without quickstart? On Tue, May 21, 2013 at 1:40 PM, Martin Grigorov wrote: > Hi Maxim, > > I guess it is related to AjaxRequestAttributes#setA

Re: Issue in 6.8.0

2013-05-20 Thread Martin Grigorov
Hi Maxim, I guess it is related to AjaxRequestAttributes#setAllowDefault(true|false) or AjaxRequestAttributes#setEventPropagation(AjaxRequestAttributes.EventPropagation.XYZ). But since the static nature of org.apache.wicket.ajax.form.AjaxFormValidatingBehavior I'm not sure how you should use #upda