You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/08/15 05:50:28 UTC

DO NOT REPLY [Bug 22414] - FileUpload default constructor doesn't work

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=22414>.
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=22414

FileUpload default constructor doesn't work

martinc@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From martinc@apache.org  2003-08-15 03:50 -------
If you want to use the default constructor, you need to call setFileItemFactory
() to set the factory before using it. It's more common to use the constructor 
that takes a factory as a parameter, though.

The point is that FileUpload can not and should not make assumptions about the 
particular factory that it uses. Initialising to DefaultFileItemFactory would 
violate that. DefaultFileItemFactory is intended to be used with 
DiskFileUpload, which is a specialisation based on storing uploaded files to 
disk. (The "Default" in the name is for historic reasons - it should really be 
DiskFileItemFactory, and will most likely be changed to that in a 2.0 release.)