[
https://issues.apache.org/jira/browse/TIKA-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698812#comment-14698812
]
Nick Burch commented on TIKA-1708:
----------------------------------
I think this is solved in r1696160. The problem was that, in the case of
explicit detector names, we were creating a second new empty mime types and
using that in the detector. I've changed it to spot this case, and instead use
the mime types the config has already created. Any chance you could test and
confirm?
> Detectors loaded from configuration files into CompositeDetector fail
> ---------------------------------------------------------------------
>
> Key: TIKA-1708
> URL: https://issues.apache.org/jira/browse/TIKA-1708
> Project: Tika
> Issue Type: Bug
> Components: config, detector
> Affects Versions: 1.10
> Reporter: Justin Palmer
> Attachments: TIKA-1708.zip
>
>
> Loading individual Detectors from a configuration file, e.g.
> <detector class="org.apache.tika.parser.microsoft.POIFSContainerDetector"/>
> <detector class="org.apache.tika.mime.MimeTypes"/>
> will cause them to be added to a CompositeDetector which does not detect,
> e.g. PST files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
