>One question I had was about backward compatibility... is there a way to >register a null or default core that reverts to the original paths? Are >there any other backward compatible gotchas (not related to custom java >code)?
I'm very excited about this patch as it would remove my current scheme of running shell scripts to hot deploy new solr webapps on the fly. Along with registering a default core so that all existing code/tests continue to work I think it would be nice to have the core name specified as a CGI param instead of (or in addition to) a url path. Otherwise, large section of client code (such as solrj/solr#) will need to be changed. For example: http://localhost:8983/solr/select?q=foo&core=core1 http://localhost:8983/solr/update?core=core1 - will
