The custom parsers and contenthandler can be configured via Tika-config. We don’t yet have a way to configure AbstractRecursive… or the DocumentSelector.
Note that 3.x beta should be out soon. Aside from requiring Java 11, there aren’t big changes in 3.x. I’ll dig up examples when I’m back to a keyboard. On Fri, Oct 13, 2023 at 6:50 AM Robert Kaulbach <[email protected]> wrote: > Hi, I have successfully used Tika 1.x as a library and ended up with some > custom classes that replaced default implementations. > - custom Parser for certain MIMEtypes. > - custom AbstractRecursiveParserWrapperHandler registered in ParseContext. > - custom Content Handler replacing Default Content Handler > - custom DocumentSelector with special rules to check if embedded content > should be parsed or not. > > > Will Tika-Server 2.x allow me to easily register these custom classes to > replace default implementations, using the classpath argument and > tika-config.xml? > -- Are there any examples to reference? > > Or would it be more realistic to keep using Tika 2.x as a library and > continue loading the custom classes through plain Java code? > > > > ------------------------------ > > ------------------------------ > This email, its contents and attachments contain information from Ziff > Davis, Inc. and/or its affiliates which may be privileged, confidential or > otherwise protected from disclosure. The information is intended to be for > the addressee(s) only. If you are not an addressee, any disclosure, copy, > distribution or use of the contents of this message is prohibited. If you > have received this email in error, please notify the sender by reply email > and delete the original message and any copies. >
