tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1145) classloaders issue loading resources when extending Tika
Date Wed, 03 Jul 2013 16:00:20 GMT

    [ https://issues.apache.org/jira/browse/TIKA-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699107#comment-13699107

Nick Burch commented on TIKA-1145:

I'm fairly sure anything with a classname starting org.eclipse.jetty will be something in
your environment, and not part of Tika

When you create a TikaConfig instance you can specify the classloader to use <http://tika.apache.org/1.3/api/org/apache/tika/config/TikaConfig.html#TikaConfig%28java.lang.ClassLoader%29>
- you can pass your own classloader in there if you want to have full control over what gets
> classloaders issue loading resources when extending Tika
> --------------------------------------------------------
>                 Key: TIKA-1145
>                 URL: https://issues.apache.org/jira/browse/TIKA-1145
>             Project: Tika
>          Issue Type: Bug
>          Components: config, mime
>    Affects Versions: 1.3
>         Environment: Tika as part of standard Solr distribution
>            Reporter: Maciej Lizewski
> I noticed that ServiceLoader is using different classloader when loading 'services' like
Parsers, etc (java.net.FactoryURLClassLoader) than MimeTypesFactory (org.eclipse.jetty.webapp.WebAppClassLoader)
when loading mime types definitions. As result - it works completely different:
> When jar with custom parser and custom-mimetypes.xml is added to solr.war - both resources
are located and loaded (META-INF\services\org.apache.tika.parser.Parser and org\apache\tika\mime\custom-mimetypes.xml)
and everything works fine.
> When jar with custom parser is in Solr core lib and configured in solrconfig.xml - only
META-INF\services\org.apache.tika.parser.Parser is loaded, but custom-mimetypes.xml is ignored.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message