Summary: | Apache POI POM should include runtime dependency on poi-ooxml | ||
---|---|---|---|
Product: | POI | Reporter: | Trejkaz (pen name) <trejkaz> |
Component: | POI Overall | Assignee: | POI Developers List <dev> |
Status: | NEEDINFO --- | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Mac OS X 10.1 |
Description
Trejkaz (pen name)
2016-08-19 01:12:02 UTC
Hmm, pesky. Some of the OOXML CT schema classes seem to be needed to power the agile encryption code. You *ought* to be able to use HSSF without needing poi-ooxml or poi-scratchpad, and you *ought* to be able to use HWPF + HSLF without needing poi-ooxml. However, this looks to be one edge case, where an apparently OLE2-only thing actually turns out to be partly OOXML under the hood. We don't want to make almost all POI OLE2-only users suck in the OOXML stuff when they don't need to Would updating the documentation, to help people know that they're accidentally roaming into OOXML territory when they might think they're still in pure-OLE2 land, be enough do you think? Maybe I just throw out that xmlbeans and update the encryption xml elements with plain DOM calls ... |