Hi, When creating a custom Solr QParser, I extended LuceneQParser which is "protected" scope. It all works as long as I put my new QParser inside solr.war, but I want to ship it as its own jar to be loaded as a plugin from external lib folder.
Problem is then that external libs are loaded using another classloader than the WAR classloader, so then even if the subclass is in same package as superclass, it is not allowed to extend a protected class, resulting in "java.lang.IllegalAccessError: class org.apache.solr.search.MaxScoreQParser cannot access its superclass org.apache.solr.search.LuceneQParser" The easiest way to resolve this would be to make LuceneQParser public, like most of the other QParsers already is. Any objection to this? It would also make it possible for company X to put their extended QParser in their own package namespace. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
