[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1329) Fileupload contentLength > maxRequestSize throws RuntimeException

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Wed May 16 20:44:52 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBSEAM-1329?page=all ]

Shane Bryzak closed JBSEAM-1329.

    Fix Version/s: 1.3.0.BETA1
       Resolution: Done
         Assignee: Shane Bryzak

I've changed it so it now throws a FileUploadException - there are other things that can go wrong besides the max request size being exceeded so the exception needs to be a little more generic.

> Fileupload contentLength > maxRequestSize throws RuntimeException
> -----------------------------------------------------------------
>                 Key: JBSEAM-1329
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1329
>             Project: JBoss Seam
>          Issue Type: Feature Request
>    Affects Versions: 1.2.1.GA
>            Reporter: Kenneth Christensen
>         Assigned To: Shane Bryzak
>            Priority: Minor
>             Fix For: 1.3.0.BETA1
> Because it's a RuntimeException I can't tell the user about the problem, e.g. file is too big. I can only show the user a standard error page :-(
> What about a MaxRequestSizeException? If I have a MaxRequestSizeException I can show the user a non-standard error page.
> e.g.
> Code:
> <pages> 
> <exception class="org.jboss.seam.MaxRequestSizeException"> 
> <redirect view-id="/uploadError.xhtml"> 
> <message>File is too big</message> 
> </redirect> 
> </exception> 
> </pages>
> Will it be possible to implement above feature in the fileupload component? 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list