Hi, On Tue, Nov 17, 2009 at 10:24 AM, Julien Nioche <lists.digitalpeb...@gmail.com> wrote: > First let me explain the classloader issue. The main class in the Tika > plugin instantiates a TikaConfig object (using Tika's XML > configuration file), which tries to load the parser classes for each > mime-type Tika knows about. Remember that we need tika-core in the > main lib directory? This is where the TikaConfig class is stored. For > some reason it is not able to find the classes in the jars located at > the plugin level even though the class instantiating TikaConfig is > itself at the plugin level.
The problem is that TikaConfig currently uses the class loader that loaded tika-core when trying to resolve the configured parser classes. There's discussion in Tika about using the Java service provider mechanism and the thread context class loader to access all available parser implementations. This would make Tika more "plugin friendly", but is not yet implemented. BR, Jukka Zitting
