commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Wiedmann (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IO-116) Replace static FileCleaner methods
Date Mon, 05 Mar 2007 12:26:50 GMT

    [ https://issues.apache.org/jira/browse/IO-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478018
] 

Jochen Wiedmann commented on IO-116:
------------------------------------

Holger, if I get you right, what you intend to tell is this:

There are a lot of places in the various commons-foo libraries, which create/destroy/manage
threads. Your recommendation is to have a management framework, where these threads can be
integrated, the target being to reduce the number of required threads.

Depending on the application (Mule in your case?), that seems a sensible request. However,
I do believe that this is clearly beyond the scope of this issue, which simply wants to create
the possibility to have a custom lifecycle at all. The question how this lifecycle is managed
can clearly be resolved later.

I must admit, that I have no idea how your concerns might be approached. I do not even know,
whether there already is an existing framework, which might be reused for that. (Quartz, may
be, but it seems the scope of Quartz is more related to the end user and not the framework
developer.) Perhaps, your ideas are sufficient for introducing a new component in the sandbox.
However, as long as there is not even an API for such a component, I see no reason to address
the integration into it here.


> Replace static FileCleaner methods
> ----------------------------------
>
>                 Key: IO-116
>                 URL: https://issues.apache.org/jira/browse/IO-116
>             Project: Commons IO
>          Issue Type: Improvement
>          Components: Utilities
>    Affects Versions: 1.3.1
>            Reporter: Jochen Wiedmann
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: commons-io-filecleaningtracker.patch
>
>
> The attached patch aims to finally resolve the problems, which are named in IO-99, FILEUPLOAD-120,
and FILEUPLOAD-125.
> I choosed a conservative strategy: Basically I copied the FileCleaner class to an instantiable
class FileCleaningTracker with instance methods. The static FileCleaner methods are now implemented
by a static instance of FileCleaningTracker. (The name FileCleaningTracker is, of course,
questionable.
> The FileCleaningTestCase was also created by simply copying FileCleaner to FileCleaningTestCase.
FileCleanerTestCase is now similarly implemented as a subclass of FileCleanerTestCase which
uses the static instance of FileCleaner rather than a dynamically created instance.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message