Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-1.8.2.GA_P03, 3.0.RC1
-
Fix Version/s: EE-1.8.2.GA_P04
-
Component/s: ICE-Components
-
Labels:None
-
Environment:-
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
The exported files are not removed from memory when they are no longer needed (e.g. navigation) or the user's session is no longer valid. The deleteOnExit flag value appears to be true but the files are not deleted until the JVM terminates, which may not happen for months or years in a production environment. We should add an API that will allow developer's to forcefully delete these files within the application.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Introduced FileResource callback registration method to notify the finishing of resource serving to interested parties. Registered callback with FileResource in DataExporter to deregister resource and remove file from the file system.
Removing the exported file after each serving it is fine in this case since the component creates the file every time is requested (to make sure its content always reflects the data table state).
Show
Mircea Toma
added a comment - Introduced FileResource callback registration method to notify the finishing of resource serving to interested parties. Registered callback with FileResource in DataExporter to deregister resource and remove file from the file system.
Removing the exported file after each serving it is fine in this case since the component creates the file every time is requested (to make sure its content always reflects the data table state).
The ResourceRegistry API already has a method defined for removing resources. The remaining work would be to modify the component so that is removes the resources it registers.