I've run into this in the past as well. Its fairly annoying. Anyone know
why the limitation? Why aren't we passing the ClassLoader thats loading
Solr classes as the parent to the lib dir plugin classloader?
- Mark
Erik Hatcher wrote:
This is probably because Solr loads its extensions from a custom class
loader, but if that class then needs to access things from the
classpath, it is only going to see the built-in WEB-INF/lib classes,
not solr/home lib JAR files. Maybe there is a Spring way to point it
at that lib directory also? This is the kinda pain we get, it seems,
when reinventing a container, unfortunately.
Erik
On May 7, 2009, at 2:49 PM, Raju444us wrote:
I have configured solr using tomcat.Everything works fine.I overrode
QParserPlugin and configured it.The overriden QParserPlugin has a
dependency
on another project say project1.So I made a jar of the project and
copied
the jar to the solr/home lib dir.
the project1 project is using spring.It has a factory class which
loads the
beans.Iam using this factory calss in QParserPlugin to get a bean.When I
start my tomcat the factory class is loading fine.But the problem is
its not
loading the beans.And Iam getting exception
org.springframework.beans.factory.BeanDefinitionStoreException:
IOException
parsing XML document from class path resource
[com/mypackage/applicationContext.xml]; nested exception is
java.io.FileNotFoundException: class path resource
[com/mypackage/applicationContext.xml] cannot be opened because it
does not
exist
Do I need to do something else?. Can anybody please help me.
Thanks,
Raju
--
View this message in context:
http://www.nabble.com/Solr-spring-application-context-error-tp23432901p23432901.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
- Mark
http://www.lucidimagination.com
