Hello.
Thanks you for the reply.
I understood using DiskFileUpload class.
It's OK in my source and test.
However, I think that FileUpload class constructer will still be a
bug.
Because, it is written to the document of FileUpload class
constructer as "which uses the default factory".
FileUpload.java 1.24
--
/**
* Constructs an instance of this class which uses the default factory to
* create <code>FileItem</code> instances.
*
* @see #FileUpload(FileItemFactory)
*/
public FileUpload()
{
super();
}
--
>Please refer to the FileUpload usage documentation, here:
>
>http://jakarta.apache.org/commons/fileupload/using.html
>
>As you will see, you should be using the DiskFileUpload class, instead of
>the FileUpload class, if you want the default disk-based implementation.
>You should use the FileUpload class itself only if you need more control
>over the way in which FileItem instances are created.
--
ume mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
