https://bz.apache.org/bugzilla/show_bug.cgi?id=59268
--- Comment #24 from Greg Woolsey <gwool...@apache.org> --- Another complication is that none of the replacement technologies that have been discussed so far can handle the arbitrary XML allowed as "extensions" in the OOXML spec. One benefit of XMLBeans is that it keeps the raw XML around and returns any properties/attributes present when asked. That way POI can "pass through" unknown content while allowing access to all known content in a file. This is used quite often by downstream projects, especially ones that start with custom "template" files containing bits like OLE components, custom Office extensions, VBA macros, complex pivot tables, etc. and fill in live data on the fly. In the spec this is handled by referencing additional namespaces on the fly by URL. Any replacement in POI would need to allow similar retention of unknown XML elements and content. This completely breaks systems like JAXB, which needs all possible namespaces and how they fit together to be defined up front. There is no dynamic model building or class loading. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
