Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-25 Thread Vladimir K
gt;>>>>> iframe so the browser performs the serialization - and that >>>>> should >>>>> >>>>>> include the button. what markup is your button attached to? >>>>&

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-20 Thread Igor Vaynberg
t;>>> >>>>>> >>>> >>>>>> -igor >>>> >>>>>> >>>> >>>>>> On Wed, Sep 9, 2009 at 8:18 PM, Vladimir Kovalyuk >>>> >>>>>> >>>> >>>>>>

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-19 Thread Vladimir K
AjaxFallbackButton("Cancel").setDefaultFormProcessing(false) >>> >>>>>>> to >>> >>>>>>> the >>> >>>>>>> multipart form and when it is pressed the form i

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-18 Thread Vladimir K
t;>> multipart form and when it is pressed the form is handled as well >> as >> >>>>>>> the >> >>>>>>> button would have defaultFormProcessing=true. >> >>>>>>> >> >>>>>>> It happens because

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-18 Thread Martin Grigorov
cause request parameters does not contain the name of > >>>>>>> the > >>>>>>> submitting button. > >>>>>>> > >>>>>>> The magic is in the new code in wicket-ajax.js > >>>>>>>

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-18 Thread Vladimir K
t;>>> >>>>>>>    // Submits a form using ajax. >>>>>>>    // This method serializes a form and sends it as POST body. >>>>>>>    submitForm: func

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-15 Thread Vladimir K
e problem is caused by handleMultipart(form) invocation. >>>>>> submitForm function accepts submitButton parameter but does not >>>>>> passes it >>>>>> to >>>>>> handleMultipart function. >>>>>> >>>>&

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-11 Thread Vladimir K
;>>>            var s = Wicket.Form.serialize(form); >>>>>            if (submitButton != null) { >>>>>                s += Wicket.Form.encode(submitButton) + "=1"; >>

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-09 Thread Vladimir K
gt;>>            if (submitButton != null) { >>>>                s += Wicket.Form.encode(submitButton) + "=1"; >>>>            } >>>>            return s; >>>>        } >>>>        return this.request.post(body); >>>>    }, >

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-09 Thread Igor Vaynberg
caused by handleMultipart(form) invocation. >>> submitForm function accepts submitButton parameter but does not passes it >>> to >>> handleMultipart function. >>> >>> Igor could you clarify that? >>> >> >> --

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-09 Thread Vladimir K
>    }, >> >> I believe the problem is caused by handleMultipart(form) invocation. >> submitForm function accepts submitButton parameter but does not passes it >> to >> handleMultipart function. >> >> Igor could you clarify that? >> > > ------------

Re: defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-09 Thread Igor Vaynberg
this bit of javascript: if (submitButton != null) { s += Wicket.Form.encode(submitButton) + "=1"; } is needed because we do perform a custom form serialization - really just constructing the query string - that we submit back to server via ajax. the multipart handling performs a regular post into

defaultFormProcessing is no longer considered when processing multipart form in ajax request

2009-09-09 Thread Vladimir Kovalyuk
I added AjaxFallbackButton("Cancel").setDefaultFormProcessing(false) to the multipart form and when it is pressed the form is handled as well as the button would have defaultFormProcessing=true. It happens because request parameters does not contain the name of the submitting button. The magic is