Hi Chris,
No. I set up a separate file, same as the wiki.
It's either a tomcat version issue or a difference between how tomcat on
my Win laptop is configured vs. the configuration on our tomcat Unix
machine.
I intend to run multiple instances of solr in production and wanted to
use the context fragments.
I have 3 test instances of solr running now (with 3 context files) and
found that whatever you set the path attribute to becomes the name of
the deployed web app (it doesn't have to match the name of the context
file, but cleaner to keep the names the same).
Here is what I found on the Apache site about this:
"The context path of this web application, which is matched
against
the beginning of each request URI to select the appropriate web
application for processing. All of the context paths within a
particular Host must be unique. If you specify a context path of an
empty string (""), you are defining the default web application for
this Host, which will process all requests not assigned to other
Contexts."
~Mike
-----Original Message-----
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 06, 2007 2:53 PM
To: solr-user@lucene.apache.org
Subject: RE: tomcat context fragment
: I've found the problem.
:
: The Context attribute path needed to be set:
:
: <Context path="/solr" docBase="/users/mp15/solr.war" debug="0"
Michael, i don't really know much about tomcat, but is this becuase you
had a single config file for all context (the examples on our wiki
suggest
that tomcat knows which contaxt path you want based on the name of hte
context fragment file)
is that something thta change between tomcat 5.0X and tomcat 5.5? (one
config file vs context fragment config files)
-Hoss
