You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/20 14:06:34 UTC
[jira] [Resolved] (WICKET-4413) Form.setMultiPart(false) does not
set the multiPart field to 0
[ https://issues.apache.org/jira/browse/WICKET-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4413.
-------------------------------------
Resolution: Not A Problem
Form#setMultiPart() switches on/off MULTIPART_HARD flag.
But a Form still can be multipart if any of its nested forms is multipart. In this case MULTIPART_HINT is set and it should not be reset manually with setMultiPart(false).
> 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