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

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

Actaully I started this ticket because I needed a possibility to force the Form 
to be set as non-multipart, even if it contains a nested multipart component.

In my case I had an inner form as part of a modal window. I could not remove it 
from being part if its outer form. So when a modal window pops up there there 
was
its form with FileUplaodField. User uploads the file then closes the modal 
window. Then does some other inputs on outer form, then submit the outer form.

When submiting outer form, there was en exception dont remeber now that it was 
something like "..wicket tries it bests to resolve the mutlipart " (or 
something like that).

Is there a way to achieve a correct behaviour when having this hierarchy of 
component in some other way then forcefully set multiPart filed on Form 
component ?
                
> 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

        

Reply via email to