[
https://issues.apache.org/jira/browse/TIKA-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245948#comment-17245948
]
Tim Allison edited comment on TIKA-3178 at 12/8/20, 3:18 PM:
-------------------------------------------------------------
Thank you, [~bob]! I made a few changes, I think, in the right direction. The
cleaner we can make the dependencies, the better. Please do edit as you see
fit!
{{xerces}} is another area for concern. We made the decision in the 1.x branch
to include it with tika-parsers so that we would have more consistency for
general users but advanced users could configure the xml parser as they wished.
{{tika-core}} tries to access xerces' SecurityManager via class.forName().
I'm not sure how best to handle this in the bundle. You'll see from the log
messages during the bundle tests, that tika-core isn't able to load xerces'
SecurityManager in the current configuration.
Again, many thanks!!!
was (Author: talli...@mitre.org):
Thank you, [~bob]! I made a few changes, I think, in the right direction. The
cleaner we can make the dependencies, the better. Please do edit as you see
fit!
{{xerces}} is another area for concern. We made the decision in the 1.x branch
to include it with tika-parsers so that we would have more consistency for
general users but advanced users could configure the xml parser as they wished.
{{tika-core}} tries to access xerces' SecurityManager via class.forName().
I'm not sure how best to handle this in the bundle. You'll see from the log
messages during the bundle tests, that tika-core isn't able to load xerces'
SecurityManager in the current configuration.
> Tika 2.0.0 -- Add back OSGi bundles for Tika parsers
> ----------------------------------------------------
>
> Key: TIKA-3178
> URL: https://issues.apache.org/jira/browse/TIKA-3178
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Blocker
> Labels: 2.0.0
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
