On Tue, 18 Oct 2011, Jukka Zitting wrote:
For my case, the class already takes a TikaConfig object, as it sometimes needs to do mimetype heirarchy and similar related stuff. Rather than wrapping that internally in a Tika object, it occured to me that parser and detector should possibly be made the sameOK, sounds reasonable. +1 to adding a getDetector() method to TikaConfig.
OK, issue opened as TIKA-755: https://issues.apache.org/jira/browse/TIKA-755 Nick
