[
https://issues.apache.org/jira/browse/TIKA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129971#comment-13129971
]
Jukka Zitting commented on TIKA-755:
------------------------------------
Hmm, I looked at the interaction between Tika and TikaConfig, and actually I
now think it's better if we leave the AutoDetectParser instantiation there.
This way the TikaConfig class is responsible for producing composite parsers
and detectors based on explicit configuration or the default classloading
mechanism, and the Tika facade (or the AutoDetectParser class directly) remains
responsible for adding autodetection and other extra features on top of the
basic configuration.
So I guess we can resolve this as fixed.
> Add getDetector() method to TikaConfig
> --------------------------------------
>
> Key: TIKA-755
> URL: https://issues.apache.org/jira/browse/TIKA-755
> Project: Tika
> Issue Type: Improvement
> Components: config
> Affects Versions: 0.10
> Reporter: Nick Burch
> Assignee: Nick Burch
> Fix For: 1.0
>
>
> As discussed on the mailing list, we should add a getDetector() method to
> TikaConfig. This would return a DefaultDetector that was created with the
> same classloader as the DefaultParser was
> As part of this, we should update the Tika class to get the DefaultDetector
> from the TikaConfig, rather than creating internally. We should also switch
> the Tika class to not create its own AutoDetectParser, but instead use the
> DefaultParser from TikaConfig
> Discussion is:
> http://mail-archives.apache.org/mod_mbox/tika-dev/201110.mbox/%3calpine.deb.2.00.1110171330160.7...@urchin.earth.li%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
