Don't know if you ever found a fix for this issue, but I saw experienced it tonight while trying to run solr through jetty in eclipse. The custom RequestHandler plugin was loading fine when running jetty normally from the command-line, but running it through eclipse hit the ClassCastException.
I found that switching to the old style of plugin-embedding (cracking open the war file and adding to WEB-INF/lib) fixed the problem. Must be something with loading from the Solr Home lib dir. -Doug Britske wrote: > > Thanks, but I'm using the updated o.a.s.handler.StandardRequestHandler. > I'm going to try on 1.2 instead to see if it changes things. > > Geert-Jan > > > > ryantxu wrote: >> >> >>> It still seems odd that I have to include the jar, since the >>> StandardRequestHandler should be picked up in the war right? Is this >>> also a >>> sign that there must be something wrong with the deployment? >>> >> >> Note that in 1.3, the StandardRequestHandler was moved from >> o.a.s.request to o.a.s.handler: >> >> http://svn.apache.org/repos/asf/lucene/solr/trunk/src/java/org/apache/solr/request/StandardRequestHandler.java >> http://svn.apache.org/repos/asf/lucene/solr/trunk/src/java/org/apache/solr/handler/StandardRequestHandler.java >> >> If you are subclassing StandardRequestHandler, make sure you are using a >> consistent versions >> >> ryan >> >> > > -- View this message in context: http://www.nabble.com/extending-StandardRequestHandler-gives-ClassCastException-tf4594102.html#a13400492 Sent from the Solr - User mailing list archive at Nabble.com.
