[ https://issues.apache.org/jira/browse/TIKA-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699793#comment-13699793 ]
Uwe Schindler commented on TIKA-1145: ------------------------------------- I think the main problem is ServiceLoader's definition. It uses context class loader to load SPIs which is in my opinion a "bug" in the spec. In Lucene we had the same problems with our own ServiceLoader impl that uses the Abstract class'/interface's classloader to loads its own implementations. See LUCENE-4713 for more info, where Lucene uses SPI to load its codecs and analyzers. > 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