Bug ID: 60153
           Summary: Use ZipEntrySource in SXSSF module
           Product: POI
           Version: 3.14-FINAL
          Hardware: PC
                OS: Mac OS X 10.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: SXSSF

The current SXSSF implementation uses temp files and this is problematic for
companies who want all their data at rest to be encrypted. added support for
developers to use their own implementations of ZipEntrySource when reading inro
XSSF workbook. I have my own subclass of this that encrypts the temp file data.
The ZipEntrySource interface is read only but it would be feasible to have
support for a writer to create ZipEntrySources too (eg something like
org.apache.poi.xssf.streaming.SheetDataWriter exposes the temp file via its
public API. If we were able to deprecate this and just provide Readers and
Writers, then this could also be subclassed to have the data in the temp file
encrypted. We could also allow a pattern where the readers and writers could be
decorated with encryptors/decryptors.

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to