Chapter 3. LifecycleManager design (Axiom 1.3)  Table of
Contents  Issues with the LifecycleManager API in Axiom 1.2.x
Cleanup strategy for temporary files  The LifecycleManager API
is used by the MIME handling code in Axiom to manage the
temporary files that are used to buffer the content of
attachment parts. The LifecycleManager implementation is
responsible to track the temorary files that have been created
and to ensure that they are deleted when they are no longer
used. In Axiom 1.2.x, this API has multiple issues and a
redesign is required for Axiom 1.3.  Issues with the
LifecycleManager API in Axiom 1.2.x    1. Temporary files that
are not cleaned up explicitly by application code will only be
removed when the JVM stops (LifecycleManagerImpl registers a
shutdown hook and maintains a list of files that need to be
deleted when the JVM exits). This means that temporary files may
pile up, causing the file system to fill.    2. LifecycleManager
also has a method deleteOnTimeInterval that deletes a file afte