Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Date: 23 Oct 2004 18:48:58 -0000
Message-ID: <20041023184858.27353.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: commons-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 31828]  -
    Size Threshold in Commons Upload not Working

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

http://issues.apache.org/bugzilla/show_bug.cgi?id=31828

Size Threshold in Commons Upload not Working

martinc@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID


------- Additional Comments From martinc@apache.org  2004-10-23 18:48 -------
All my testing shows that zero-length files are not written to disk unless you 
choose to do that after they have been uploaded. If you can provide a test case 
that demonstrates that I am wrong, then I'll be happy to fix the bug.

As for the comments on the design of FileUpload, they really have nothing to do 
with this bug, and so have no business here. However, note that (a) you can use 
your own FileItem implementation with DiskFileUpload as long as your factory 
extends DefaultFileItemFactory, and (b) you can use the FileUpload class to 
provide your own implementation that is not related to DiskFileUpload (e.g. if 
you wanted to store the file items in a database).

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