On Wed, Aug 26, 2015 at 6:11 AM, Nick Burch
wrote:
> You probably shouldn't be defining additional mimetypes to
> DefaultParser.
I had an impression that indeed there should be no explicit definition
and new types should be hooked up to a default parser automatically via
the service loader. But
That’s on my todo list (TIKA-1508). Unfortunately, that doesn’t exist yet.
I’d recommend for now following the pattern of the PDFParser or the
TesseractOCRParser. The config is driven by a properties file.
As soon as my dev laptop becomes unbricked, I’m going to turn to TIKA-1508.
Given my
On Thu, 27 Aug 2015, Andrea Asta wrote:
This parser needs some configuration to init an external connections. Is
there a way to specify the constructor params (or bean properties to
set) in the Tika xml format?
Nope, not yet. See the thread "Configuring parsers and translators" for
some discu
Hi all,
I've developed a new Parser for my custom file type.
This parser needs some configuration to init an external connections. Is
there a way to specify the constructor params (or bean properties to set)
in the Tika xml format?
Thanks
Andrea
