: I would write an own RH for my system. is an howto in the www ? i didnt : found anythin about it.
I would start by looking at how existing RequestHandlers are implemented -- the ones that ship with Solr are heavily refactored to reuse a lot of functionality, which can sometimes make it hard to follow what's going on, but at he same time they help make it clear where there is functionality you can reuse. My other big tip would be: rethink wether you really need to write RequestHandler. once upon a time this was the main type of "plugin" for doing things at search time, but with the introduction of QParsers and SearchComponents there is now usually a lot easier ways to do things -- if you tell us what type of custom logic you want to write, folks might be able to point out a simpler way to implement it. : can i develop in the svn-checkout and test in without building an new : solr.war ? debug ? .... if you take a look at the JARs that are included in the Solr release, you can compile against them -- you also don't have to rebuild the WAR with your custom classes, you can put them in a Jar that is loaded at runtime... http://wiki.apache.org/solr/SolrPlugins As for debugging Plugins: i tend to do it all via UnitTests and stack traces. there are some base classes in Solr that make this fairly easy to setup (TestHarness, AbstractSolrTestCase, and the new JUNit4 test base class whose name escapes me at hte moment) : i setting up solr in eclipse like this: : http://www.lucidimagination.com/developers/articles/setting-up-apache-solr-in-eclipse : but so its not possible to develop, right ? can you clarify your question? ... if you followed those steps i'm not sure why you wouldn't be able to develope your plugin and test it in eclipse. -Hoss
