[jira] [Commented] (WICKET-4413) Form.setMultiPart(false) does not set the multiPart field to 0

["Tomas Bilka (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211158#comment-13211158 ] 

Tomas Bilka commented on WICKET-4413:
-------------------------------------

One clarification. The reset to 0 works when the multiPart value is 1 (0000000000000000000000000000001b) but it does not work for multipart of value 2 (0000000000000000000000000000010b).
For value 2, after "AND"ing with ~MULTIPART_HARD == 11111111111111111111111111111110b, the result would be  0000000000000000000000000000010b which is still 2.
                
> Form.setMultiPart(false) does not set the multiPart field to 0
> --------------------------------------------------------------
>
>                 Key: WICKET-4413
>                 URL: https://issues.apache.org/jira/browse/WICKET-4413
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.3
>         Environment: Windows 7 (64 bit), Intel i3 platform
>            Reporter: Tomas Bilka
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> My expectation is that by calling setMutliPart(false) the mutliPart field in Form component should be set to 0.
> This line of code from org.apache.wicket.markup.html.form.Form<T>: multiPart &= ~MULTIPART_HARD; is probably trying to reset the multiPart to 0 (this is how i understand it), but it fails to do so since
> ~MULTIPART_HARD == 11111111111111111111111111111110  (initial value of MULTIPART_HARD is 1 or 0000000000000000000000000000001 in binary)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira