You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Guillaume Mary (JIRA)" <ji...@apache.org> on 2013/05/15 15:39:15 UTC
[jira] [Commented] (WICKET-5190) Overriding
Form.onFileUploadException in nested forms
[ https://issues.apache.org/jira/browse/WICKET-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658359#comment-13658359 ]
Guillaume Mary commented on WICKET-5190:
----------------------------------------
2 discussions related to this issue:
http://apache-wicket.1842946.n4.nabble.com/Overriding-Form-onFileUploadException-in-nested-forms-td4657874.html
http://apache-wicket.1842946.n4.nabble.com/Manage-exceptions-on-a-nested-multipart-upload-form-td4658815.html
> Overriding Form.onFileUploadException in nested forms
> -----------------------------------------------------
>
> Key: WICKET-5190
> URL: https://issues.apache.org/jira/browse/WICKET-5190
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.6.0, 1.5.10
> Reporter: Guillaume Mary
> Attachments: quickStartOnFileUploadFormException.zip
>
>
> If the upload exceeds the allowed max size, the
> SizeLimitExceededException is caught in the outer form, i.e. the
> form to which the upload component was added. Thus, I cannot
> override Form.onFileUploadException in my inner form and thus
> not implement a custom handling (this is necessary, as in this
> case I need to explicitly call FeedbackPanel.error on my upload
> component's FeedbackPanel and add update it via Ajax). Adding
> custom code to the outer form is not an option as this way I'd
> have to modify all users of my upload component.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira