[
https://issues.apache.org/jira/browse/CONNECTORS-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153180#comment-16153180
]
Karl Wright commented on CONNECTORS-1453:
-----------------------------------------
I've actually just tried the POI team's proposed non-temporary fix to this
problem and it works fine, and will be present (I'm told) in POI 3.18. So,
when that comes out, we'll be able to just switch over to doing things the old
way.
> Implement POI's suggested workaround for their classloader issue
> ----------------------------------------------------------------
>
> Key: CONNECTORS-1453
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1453
> Project: ManifoldCF
> Issue Type: Bug
> Components: Tika extractor
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 2.9
>
>
> The Apache POI folks do not want to change their classloader setup,
> unfortunately. But they have provided a hook for overriding the class loader
> in 3.16 and up here:
> {code}
> org.apache.poi.POIXMLTypeLoader.setClassLoader(ClassLoader cl)
> {code}
> This sets the classloader into a ThreadLocal. So there would be a rather
> clunky workaround that would have the TikaExtractor set the POI class loader
> before all tika-parser requests.
> It only makes sense to do this if there is no plan to solve this for real.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
