+ // We need to ensure that the database points to a place where it makes
+ // sense. If the path in the system.xml file is an absolute path, then
+ // honor it. If it's not, we first check for the system property "xindice.db.home"
+ // and if the lookup is successful we use it as the database root parent. If
+ // the property is not set, we use /WEB-INF relative to the servlet context, unless
+ // the war has not been unpacked. In this case, we throw an exception and + // ask the user to specify the location of database root
Why does a relative path not make sense?
Since this is not an "out-of-the-box" solution anymore (the user will have to either specify the xindice.db.home variable or modify the system.xml file) why do we have to guess what the right thing is when it would be so much easier to let the user provide it :
1) create the xindice directory under your webapp server "webapps" directory. For Tomcat:
mkdir /usr/local/java/jakarta-tomcat/webapps/xindice-1.1b
2) unpack the release into that directory
unzip xindice/dist/xindice-1.1.war -d /usr/local/java/jakarta-tomcat/webapps/xindice-1.1b
3) edit the file /usr/local/java/jakarta-tomcat/webapps/xindice-1.1b/WEB-INF/system.xml and modify the dbroot property to point to a valid location
4) edit your webapp server configuration file and register the xml-xindice component. For Tomcat, copy the following lines into the appropriate location (following the <Host> tag) of the conf/server.xml file:
<Context path="/Xindice"
docBase="/usr/local/java/jakarta-tomcat/webapps/xindice-1.1b"
debug="0" reloadable="true">
<Logger className="org.apache.catalina.logger.FileLogger"
debug="0" verbosity="1" prefix="xindice_log."
directory="logs" timestamp="true" suffix=".txt"/>
</Context>5) start your webapp server
If the user has problem following these instructions, I think he has more important problems to solve.
-Vladimir
-- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
