https://bz.apache.org/bugzilla/show_bug.cgi?id=61478
Bug ID: 61478
Summary: POI OOXML-Schema lookup uses wrong classloader
Product: POI
Version: unspecified
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: POI Overall
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
When poi-ooxml uses reflection to locate classes in poi-ooxml-schema, it
apparently does not use the classloader of the current class or thread to do
this. As a result, you cannot get poi-ooxml to work properly in a non-root
classloader.
Furthermore, even if you move poi-ooxml-schema to the root level, it has
callbacks into poi-ooxml, so you are forced to move THAT jar to root level as
well. And once you do that, poi-ooxml calls back to org.apache.poi.util, which
is in poi.jar, so that jar also needs to be run at root level.
(A side note: having poi and poi-ooxml and poi-ooxml-schemas be separate makes
little sense if they all depend on each other in this way.)
We discovered this trying to integrate the latest Tika (which uses POI version
3.9) with ManifoldCF. ManifoldCF runs tika-parsers at the connector level,
which has its own classloader. We were forced to move all of POI, and its
dependencies, to the root classloader level, which greatly increases the size
of our binary image.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
