>Since it would be read-only, would it just be another option, instead of a
>full replacement?
Y, think of it like XSSF's eventusermodel. We define an interface for what a
user will have to react to, like XSSFSheetXMLHandler's SheetContentsHandler,
and we take care of the rest. You can see
Late to the party as I sift through my Spring Break email backlog.
Since it would be read-only, would it just be another option, instead of a
full replacement? Would the data model need to be more fully fleshed out
to support all the corners of the OOXML spec not currently represented?
Is there
Absolutely!
Since XMLBeans is collecting cobwebs in the attic, we've been looking for a
replacement, so long as it doesn't grow the POI codebase too much.
On Apr 4, 2017 5:29 AM, "Allison, Timothy B." wrote:
Thank you, Javen.
On Tika, we now have mostly bean-free SAX-based parsers for docx and
