In regard to the comment about lack of an interface, I view this as a benefit of the tool.
Whether I'm developing with Python, PHP, Coldfusion, .NET, Java, etc. I can create my own customizable interface. As a coldfusion programmer with moderate programming capabilities, this tool is perfect for my needs. On 9/8/06, Andrew May <[EMAIL PROTECTED]> wrote:
Chris Hostetter wrote: > : Nice. Is the same doable under Jetty? (never had to deal with JNDI > : under Jetty) > > i haven't tried it personally, but according to Yoav "reading" JNDI > options is part of hte Servlet Spec, and billa found a refrene to > useing "<env-entry>" to do so... > > http://www.nabble.com/Re%3A-multiple-solr-webapps-p3991310.html > > ...where exactly that option goes in Jetty's configuration isn't something > i'm clear on. > <env-entry> values go in web.xml, so it would mean having modified versions of solr.war for each collection. <env-entry> is an optional part of the Servlet spec for standalone servlet implementations. The basic version of Jetty does not have any JNDI support, you need to use JettyPlus (http://jetty.mortbay.org/jetty5/plus/index.html) for that. -Andrew
