commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <>
Subject [jira] [Updated] (FILEUPLOAD-155) Fix documentation on resource clean up in conjunction with DiskFileItemFactory
Date Wed, 06 Mar 2013 18:32:14 GMT


Simone Tripodi updated FILEUPLOAD-155:

    Fix Version/s:     (was: 1.3)
> Fix documentation on resource clean up in conjunction with DiskFileItemFactory
> ------------------------------------------------------------------------------
>                 Key: FILEUPLOAD-155
>                 URL:
>             Project: Commons FileUpload
>          Issue Type: Improvement
>    Affects Versions: 1.2.1
>            Reporter: Jörg Heinicke
>            Assignee: Jochen Wiedmann
>            Priority: Minor
>             Fix For: 1.2.2
> 1.
> "return new DiskFileItemFactory(fileCleaningTracker, DiskFileItemFactory.DEFAULT_SIZE_THRESHOLD,
> DiskFileItemFactory does not have such a constructor.
> 2.
> "When using the DiskFileItemFactory, then you should consider the following: Temporary
files are automatically deleted as soon as they are no longer needed. (More precisely, when
the corresponding instance of File is garbage collected.) Cleaning up those files is done
by an instance of FileCleaningTracker, and an associated thread. In a complex environment,
for example in a web application, you should consider terminating this thread, for example,
when your web application ends. See the section on "Resource cleanup" in the users guide of
> That's at least not precise. By default there is no FileCleaningTracker.
> 3.
> "Returns: An instance of FileCleaningTracker, defaults to FileCleaner.getInstance().
Null, if temporary files aren't tracked."
> There is no default tracker.
> 4.
> "Returns the tracker, which is responsible for deleting temporary files."
> Obviously wrong for setter. Copy&Paste error from getter.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message