jFM sounds good... I have written a little stand-alone Servlet that reads in the XML/TXT Solr configuration files using Apache Commons IO, outputs the current content for editing and writes it back to the file system and after that I fire a CURL request from my (PHP based) administration panel to reload the core...

cheers
Stefan

Am 15.06.2011 10:10, schrieb Paul Libbrecht:
Though not with webdav (which is underdefined to my taste and seems only to be 
working with common implementations such as mod_dav), I had success with jFM (I 
used version 0.95):
        http://java.net/projects/jfm

maybe that helps?

paul


Le 15 juin 2011 à 09:55, Erik Hatcher a écrit :

Rather than reinventing wheels here, I think that fronting the conf/ directory 
with a WebDAV server would be a great way to go.  I'm not familiar with the 
state-of-the-art of WebDAV servers these days but there might be something 
pretty trivial that can be configured in Tomcat to do this?  Or maybe some 
servlet (or .war) that can be installed?


On Jun 14, 2011, at 16:29 , Way Cool wrote:

+1 Good idea! I was thinking to write a web interface to change contents for
elevate.xml and feed back to Solr core.

On Tue, Jun 14, 2011 at 1:51 PM, Markus Jelsma
<markus.jel...@openindex.io>wrote:

There is no API. Upload and restart the core is the way to go.

Does anyone have any examples of modifying a configuration file, like
"elevate.xml" from a browser? Is there an API that would help for this?

If nothing exists for this, I am considering implementing something that
would change the "elevate.xml" file then reload the core. Or is there a
better approach for dynamic configuration?

Thank you.

.


--
Mit den besten Grüßen aus Nürnberg,
Stefan Moises

*******************************************
Stefan Moises
Senior Softwareentwickler

shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck

Tel.: 0911/25566-25
Fax:  0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
*******************************************


Reply via email to