Re: getInputAsArray behavior

2018-02-04 Thread Maxim Solodovnik
Actually this issue is reproducible in our project with select2 field MultiSelect from here: https://github.com/wicketstuff/core/tree/master/select2-parent Will try to test using select2 example projects On Mon, Feb 5, 2018 at 1:56 PM, Sven Meier wrote: > Hi Maxim, > > are you

Re: getInputAsArray behavior

2018-02-04 Thread Sven Meier
Hi Maxim, are you using multipart requests? If not, there shouldn't be any change in serializing the input fields. I've tried Ajax and non-Ajax requests but cannot reproduce the problem. Are you entering "[null] into a field, without quotes but *with* square brackets? Sven Am 05.02.2018

Re: getInputAsArray behavior

2018-02-04 Thread Maxim Solodovnik
Hello Sven, The issue is caused by this [1] commit the form is now being serialized differently Previously FormComponent.getInputAsArray method got (Object)null as input Right now it is [null] as List [1] https://github.com/apache/wicket/commit/f642f4ad4266319731b200e517eadf53fef5a56b On

Re: getInputAsArray behavior

2018-02-04 Thread Sven Meier
Hi, Investigation shows "[null]" string is being converted to ["null"] (new String[]{"null"}) by FormComponent.getInputAsArray method "null" does not seem right. Can you pin down this problem to a recent commit in Wicket? I don't remember any change in FormComponent related to this. Regards

getInputAsArray behavior

2018-02-04 Thread Maxim Solodovnik
Hello All, 'master' branch of our main application is based on 8.0.0-SNAPSHOT Tonight we have error report: our latest build fails without changes in our code Investigation shows "[null]" string is being converted to ["null"] (new String[]{"null"}) by FormComponent.getInputAsArray method I see

Re: 8.0.0 blockers

2018-02-04 Thread Korbinian Bachl
Hello Kamil, be careful when using this feature in production as there is a race condition meaning it depends on network, browser and client thread count if it works or not. - Ursprüngliche Mail - > Von: "Kamil Paśko" > An: dev@wicket.apache.org > Gesendet:

[GitHub] wicket pull request #264: WICKET-6526 check HTTP method for all form submiss...

2018-02-04 Thread duesenklipper
GitHub user duesenklipper opened a pull request: https://github.com/apache/wicket/pull/264 WICKET-6526 check HTTP method for all form submissions this moves the HTTP method check from onFormSubmitted to onFormSubmitted(submitter) so that every form submission performs this

[GitHub] wicket pull request #263: WICKET-6526 check HTTP method for all form submiss...

2018-02-04 Thread duesenklipper
GitHub user duesenklipper opened a pull request: https://github.com/apache/wicket/pull/263 WICKET-6526 check HTTP method for all form submissions this moves the HTTP method check from onFormSubmitted to onFormSubmitted(submitter) so that every form submission performs this

[GitHub] wicket pull request #262: WICKET-6526 check HTTP method for all form submiss...

2018-02-04 Thread duesenklipper
GitHub user duesenklipper opened a pull request: https://github.com/apache/wicket/pull/262 WICKET-6526 check HTTP method for all form submissions this moves the HTTP method check from onFormSubmitted to onFormSubmitted(submitter) so that every form submission performs this