DO NOT REPLY [Bug 17106] New: - File upload exceptions.

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17106>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17106

File upload exceptions.

           Summary: File upload exceptions.
           Product: Commons
           Version: 1.0 Alpha
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: File Upload
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: kevin@minshull.ca


I have been using the file upload for handling my requests and i quite like 
what there is so far.  The reason that i chose this over the servlets.com file 
upload is because this is able to handle the file too large with an exception.  
I am actively using it in the development of my website and in the testing and 
development it works just as good as the servlets.com file upload so far.  I 
have not yet stressed it though.
 
However i would like to suggest to take one more step.  I suggest you throw the 
usual FileUploadException when "the request was rejected because it's size 
exceeds the allowed range" and throwing something to the effect of a 
FileUploadRequestException as "the request doesn't contain a multipart/form-
data..."
 
This is the reason that i chose the product, and am continuing to use it, but i 
wish there was a more defined way to know about the size exception instead of 
doing a string check on the exception message.

Thx for your time to read this.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org