Hi All
As of a month or two back, now have a DefaultDetector, which does nifty
service loading to find all the available detectors. This replaces the
ContainerAwareDetector, and works in very much the same way as the default
parser does.
Would it make sense to add a getDetector() method to T
Hi,
On Mon, Oct 17, 2011 at 2:32 PM, Nick Burch wrote:
> Would it make sense to add a getDetector() method to TikaConfig to mirror
> the parser one? It's only a few lines of code without it, but it seems to me
> that it'd make things simpler and cleaner if it was there. Thoughts?
Why not just us
On Mon, 17 Oct 2011, Jukka Zitting wrote:
On Mon, Oct 17, 2011 at 2:32 PM, Nick Burch wrote:
Would it make sense to add a getDetector() method to TikaConfig to mirror
the parser one? It's only a few lines of code without it, but it seems to me
that it'd make things simpler and cleaner if it was
[
https://issues.apache.org/jira/browse/TIKA-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128924#comment-13128924
]
Michael McCandless commented on TIKA-753:
-
OK I committed this; I'll leave it open s
Hi,
On Mon, Oct 17, 2011 at 3:56 PM, Nick Burch wrote:
> My idea for wanting to get via the TikaConfig is based on the two arguments
> that DefaultDetector takes. One is the mime registry, which TikaConfig
> provides, the other is the classloader which TikaConfig may have been passed
OK, I see t
