[ 
https://issues.apache.org/jira/browse/WICKET-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Grigorov resolved WICKET-5190.
-------------------------------------

    Resolution: Won't Fix

Closing as "Won't fix" because we have no good solution for this problem and 
there is a workaround.

> 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 1.5.10.zip, 
> quickStartOnFileUploadFormException 6.8.0.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 was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to