A customer has the following dataExporter issues. They have a custom outputTypeHandler defined like so:

<ice:dataExporter outputTypeHandler="#{table.excelDataTableExporter}" ... />

The 'table' managed bean creates an instance of the custom class which extends com.icesoft.faces.component.dataexporter.ExcelOutputHandler and helps retrieve cell content/data depending on column. However I don't think this matters but worth mentioning. Here are their issues:

1: The ExcelOutputHandler accepts a path as an input parameter and creates a blank excel file in it's constructor. If the user does not end up exporting the table, a blank excel file is still created on the server. If an application has 20-30 tables in it, these files will begin to accumulate rapidly. We should ensure that a file is only created when actually exporting the date.

2: This may be related to 2. 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.