Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

Thanks Martin, This is good news. Looking forward to 6.24.0. Kind regards, Fabio On Fri, Jun 17, 2016 at 10:26 AM, Martin Grigorov wrote: > Hi Fabio, > > I agree that the removal of the default message is not really needed. > It has been done with

Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

Hi Fabio, I agree that the removal of the default message is not really needed. It has been done with https://issues.apache.org/jira/browse/WICKET-5735. I've reverted this with https://issues.apache.org/jira/browse/WICKET-6181 Martin Grigorov Wicket Training and Consulting

Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

Hi all, Does anybody have any feedback on this? Many thanks, Fabio On Tue, May 31, 2016 at 12:46 PM, Fabio Fioretti < windom.macroso...@gmail.com> wrote: > Hi Martin, > > You are right, the form id was already there in 6.17.0, but the default > message was removed! That is what is breaking my

Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

Hi Martin, You are right, the form id was already there in 6.17.0, but the default message was removed! That is what is breaking my app - I did not realize it because my custom message was the same as the default. Why was it removed? In 6.17.0: final String defaultValue = "Upload must be less

Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

Hi, On Fri, May 27, 2016 at 12:42 PM, Fabio Fioretti < windom.macroso...@gmail.com> wrote: > Hi Martin, > > Is this the ticket you refer to? > https://issues.apache.org/jira/browse/WICKET-5190 Yes, this is the one! > > > It has an explanation on why onFileUploadException() is called on the

Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

As a side note: finalMaxSize does have a setter in Form, sorry for the oversight. However, setting finalMaxSize on form0 has no effect... Only the one on form1 (the outer form) is actually enforced, but then again, properties must be defined at that level. Thanks, Fabio On Fri, May 27, 2016 at

Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

Hi Martin, Is this the ticket you refer to? https://issues.apache.org/jira/browse/WICKET-5190 It has an explanation on why onFileUploadException() is called on the root form that seems reasonable. In any case, if I don't specify the form id in the property key (leaving just "uploadTooLarge") I

Re: AjaxFormSubmitBehavior, FileUploadField and nested forms.

Hi, I believe there is/was another ticket describing exactly your problem but I cannot find it now. The form id in the property key is not really needed. You could use it to give Wicket a more specific message for particular component. You can remove it if this message should/could be used for

AjaxFormSubmitBehavior, FileUploadField and nested forms.

Hello everybody, I recently migrated an application from Wicket 6.17.0 to 6.23.0 and I'm experiencing the following problem. I have 2 nested forms. The inner one, form0, contains a FileUploadField with an AjaxFormSubmitBehavior(form0, "change") attached to it, while the external one, form1,