Apache POI

The name was originally an acronym for "Poor Obfuscation Implementation",^[2] referring humorously to the fact that the file formats seemed to be deliberately obfuscated, but poorly, since they were successfully reverse-engineered. This explanation – and those of the similar names for the various sub-projects – were removed from the official web pages in order to better market the tools to businesses who would not consider such humor appropriate. The original authors (Andrew C. Oliver and Marc Johnson) also noted the existence of the Hawaiian poi dish, made of mashed taro root, which had similarly derogatory connotations.^[3]

POI supports the ISO/IEC 29500:2008 Office Open XML file formats since version 3.5. A significant contribution for OOXML support came from Sourcesense,^[4] an open source company which was commissioned by Microsoft to develop this contribution.^[5] This link spurred controversy, some POI contributors questioning POI OOXML patent protection regarding Microsoft's Open Specification Promise patent license.^[6]

The Apache POI project contains the following subcomponents (meaning of acronyms is taken from old documentation):

• POIFS (Poor Obfuscation Implementation File System^[2]) – This component reads and writes Microsoft's OLE 2 Compound document format. Since all Microsoft Office files are OLE 2 files, this component is the basic building block of all the other POI elements. POIFS can therefore be used to read a wider variety of files, beyond those whose explicit decoders are already written in POI.
• HSSF (Horrible SpreadSheet Format^[2]) – reads and writes Microsoft Excel (XLS) format files. It can read files written by Excel 97 onwards; this file format is known as the BIFF 8 format. As the Excel file format is complex and contains a number of tricky characteristics, some of the more advanced features cannot be read.
• XSSF (XML SpreadSheet Format) – reads and writes Office Open XML (XLSX) format files. Similar feature set to HSSF, but for Office Open XML files.
• HPSF (Horrible Property Set Format^[2]) – reads "Document Summary" information from Microsoft Office files. This is essentially the information that one can see by using the File|Properties menu item within an Office application.
• HWPF (Horrible Word Processor Format^[7]) – aims to read and write Microsoft Word 97 (DOC) format files. This component is in initial stages of development.
• XWPF (XML Word Processor Format^[7]) – similar feature set to HWPF, but for Office Open XML files.
• HSLF (Horrible Slide Layout Format^[7]) – a pure Java implementation for Microsoft PowerPoint files. This provides the ability to read, create and edit presentations (though some things are easier to do than others)
• XSLF (Open Office XML Slideshow Format)
• HDGF (Horrible DiaGram Format^[7]) – an initial pure Java implementation for Microsoft Visio binary files. It provides an ability to read the low level contents of the files.
• HPBF (Horrible PuBlisher Format^{[citation needed]}) – a pure Java implementation for Microsoft Publisher files.^[8]
• HSMF (Horrible Stupid Mail Format^{[9][better source needed]}) – a pure Java implementation for Microsoft Outlook MSG files.^[10]
• DDF (Dreadful Drawing Format^[7]) – a package for decoding the Microsoft Office Drawing format.
• XDDF (XML Dreadful Drawing Format)

The HSSF component is the most advanced feature of the library.^[11] Other components (HPSF, HWPF, and HSLF) are usable, but less full-featured.^[12][13]

The POI library is also provided as a Ruby^[14] or ColdFusion extension.

There are modules for Big Data platforms (e.g. Apache Hive/Apache Flink/Apache Spark), which provide certain functionality of Apache POI, such as the processing of Excel files.^[15][16]

• Open Packaging Conventions
• Office Open XML software

• Official website