I was also able to reproduce this issue.
When I stepped through the code with NestedForm, the Form.handleMultiPart()
never creates a MultipartWebRequest due to the original request is
identified as an AjaxRequest (as seen by the following code snippet.
<code>
protected boolean handleMultiPart()
{
if (isMultiPart() && !((WebRequest)getRequest()).isAjax())
{
...
</code>
However, when I step through a non-nested Form example (with a File upload)
but utilize an Ajax call, the isAjax() is false. Which indicates that the
seamless iframe fix is working.
(https://issues.apache.org/jira/browse/WICKET-2420)
Back to the nested form example, I even set the Outer form to be multipart
but it still doesn't work (ajax is still true).
Where is this seamless Iframe fix so I can see where it is applied and why
it is not being used even if the form is set to multi-part?
Thanks
- Doug
--
View this message in context:
http://old.nabble.com/FileUploadField-in-a-ModalWindow-%28wicket-1.4.3%29--tp26577255p26635765.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
