gianugo 2002/12/04 15:28:12
Modified: src/documentation/content/xdocs/dev guide-internals.xml
Log:
Added informations about the new behaviour in calculating the database root
Revision Changes Path
1.6 +11 -6
xml-xindice/src/documentation/content/xdocs/dev/guide-internals.xml
Index: guide-internals.xml
===================================================================
RCS file:
/home/cvs/xml-xindice/src/documentation/content/xdocs/dev/guide-internals.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- guide-internals.xml 4 Dec 2002 16:24:43 -0000 1.5
+++ guide-internals.xml 4 Dec 2002 23:28:12 -0000 1.6
@@ -110,11 +110,16 @@
<p>The important elements in this configuration file are:</p>
<ul>
<li>the <code>dbroot</code> attribute of the
<code>root-collection</code>
- element. It is a directory path (absolute or
relative; if relative,
- it is assumed to be relative to the
<code>XINDICE_HOME</code>
- environment variable), pointing to the <em>database
root</em> directory of the
- database instance. Recall that this is where Xindice
stores all its data and
- meta-data files.</li>
+ element. It is a directory path that can be absolute
or relative. If absolute,
+ Xindice will use it right away, if relative,
+ Xindice will try to find a system property called
<code>xindice.db.home</code> and
+ append to it the value of the "dbroot" attribute. If
such system property
+ is not set, Xindice will try to use the
<code>/WEB-INF</code> webapp directory (under
+ Tomcat it will be something like
<code>[TOMCAT_HOME]/webapps/Xindice/WEB-INF</code>
+ as the parent (be aware that in case of a webapp
upgrade it's possible to lose the
+ whole database). If even that fails (e.g. because
the WAR file was not unpacked),
+ an Exception will be thrown and Xindice will fail to
initialize with a proper
+ log message suggesting a solution.</li>
<li>the <code>name</code> attribute of the
<code>root-collection</code> element.
The root collection (or database) in Xindice is not
called simply "/" as
you may have expected. It actually has a name; this
name is specified here.</li>