Forgot to escape < and > characters.

git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@150833 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Kelvin Tan 2002-09-17 04:00:11 +00:00
parent 25926e6866
commit 03974c1029
1 changed files with 29 additions and 29 deletions

View File

@ -45,7 +45,7 @@
</p> </p>
<p> <p>
Voila! You should now have a jar file "indyo-<version number>.jar". Voila! You should now have a jar file "indyo-&lt;version number&gt;.jar".
</p> </p>
</section> </section>
@ -62,9 +62,9 @@
<section name="Step 4: Using Indyo"> <section name="Step 4: Using Indyo">
<p> <p>
Congratulations, you have finally reached the fun the Congratulations, you have finally reached the fun the
part of this tutorial. This is where you'll discover part of this tutorial. This is where you'll discover
the power of Indyo. the power of Indyo.
</p> </p>
<p> <p>
@ -76,7 +76,7 @@
<source><![CDATA[ <source><![CDATA[
IndexDataSource ds = new FSDataSource("/usr/local/lucene/docs"); IndexDataSource ds = new FSDataSource("/usr/local/lucene/docs");
IndyoIndexer indexer = new IndyoIndexer("/usr/local/index", IndyoIndexer indexer = new IndyoIndexer("/usr/local/index",
"/usr/local/indyo/default.config.xml"); "/usr/local/indyo/default.config.xml");
indexer.index(ds); indexer.index(ds);
]]></source> ]]></source>
@ -92,11 +92,11 @@ indexer.index(ds);
</p> </p>
<p> <p>
Get familiar with FSDataSource. You'll find it very handy, both for indexing Get familiar with FSDataSource. You'll find it very handy, both for indexing
files directly, as well as nesting it within another datasource. For example, files directly, as well as nesting it within another datasource. For example,
you might need to index a database table, in which one of the rows represent you might need to index a database table, in which one of the rows represent
the location of a file, and you may want to use FSDataSource to index this the location of a file, and you may want to use FSDataSource to index this
file as well. file as well.
</p> </p>
<subsection name="Writing your custom IndexDataSource"> <subsection name="Writing your custom IndexDataSource">
@ -147,13 +147,13 @@ public class HashMapDataSource implements IndexDataSource
</p> </p>
<p> <p>
A slightly more useful IndexDataSource, SingleDocumentFSDataSource A slightly more useful IndexDataSource, SingleDocumentFSDataSource
provides an example of how to nest datasources. Given a directory, provides an example of how to nest datasources. Given a directory,
SingleDocumentFSDataSource recursively indexes all directories SingleDocumentFSDataSource recursively indexes all directories
and files within that directory <i>as the same Document</i>. In other and files within that directory <i>as the same Document</i>. In other
words, only one Document is created in the index. This is accomplished words, only one Document is created in the index. This is accomplished
by the use of a nested datasource. The code for by the use of a nested datasource. The code for
SingleDocumentFSDataSource is listed below: SingleDocumentFSDataSource is listed below:
</p> </p>
<source><![CDATA[ <source><![CDATA[
@ -177,12 +177,12 @@ public class SingleDocumentFSDataSource
]]></source> ]]></source>
<p> <p>
Nested datasources don't result in a separate Document being created. Nested datasources don't result in a separate Document being created.
Use them when working with complex datasources, i.e., datasources Use them when working with complex datasources, i.e., datasources
which are an aggregation of multiple datasources. The current way to which are an aggregation of multiple datasources. The current way to
add a nested datasource is using the key "NESTED_DATASOURCE". Indyo add a nested datasource is using the key "NESTED_DATASOURCE". Indyo
accepts an IndexDataSource object, a List of IndexDataSources, accepts an IndexDataSource object, a List of IndexDataSources,
or an IndexDataSource[] for this key. or an IndexDataSource[] for this key.
</p> </p>
</subsection> </subsection>
@ -208,10 +208,10 @@ public class SingleDocumentFSDataSource
<section name="Acknowledgements"> <section name="Acknowledgements">
<p> <p>
This document was shamelessly ripped from the extremely well-written This document was shamelessly ripped from the extremely well-written
and well-organized and well-organized
<a href="http://jakarta.apache.org/turbine/torque/tutorial.html">Torque <a href="http://jakarta.apache.org/turbine/torque/tutorial.html">Torque
</a> tutorial. Thanks Pete! </a> tutorial. Thanks Pete!
</p> </p>
</section> </section>