diff --git a/sandbox/contributions/indyo/xdocs/tutorial.xml b/sandbox/contributions/indyo/xdocs/tutorial.xml index 7da3603d5cd..3f1a282fb1e 100644 --- a/sandbox/contributions/indyo/xdocs/tutorial.xml +++ b/sandbox/contributions/indyo/xdocs/tutorial.xml @@ -45,7 +45,7 @@
- Voila! You should now have a jar file "indyo-
- Congratulations, you have finally reached the fun the - part of this tutorial. This is where you'll discover - the power of Indyo. + Congratulations, you have finally reached the fun the + part of this tutorial. This is where you'll discover + the power of Indyo.
@@ -76,8 +76,8 @@
@@ -92,11 +92,11 @@ indexer.index(ds);
- 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, - 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 - file as well. + 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, + 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 + file as well.
- A slightly more useful IndexDataSource, SingleDocumentFSDataSource - provides an example of how to nest datasources. Given a directory, - SingleDocumentFSDataSource recursively indexes all directories - and files within that directory as the same Document. In other - words, only one Document is created in the index. This is accomplished - by the use of a nested datasource. The code for - SingleDocumentFSDataSource is listed below: + A slightly more useful IndexDataSource, SingleDocumentFSDataSource + provides an example of how to nest datasources. Given a directory, + SingleDocumentFSDataSource recursively indexes all directories + and files within that directory as the same Document. In other + words, only one Document is created in the index. This is accomplished + by the use of a nested datasource. The code for + SingleDocumentFSDataSource is listed below:
-- Nested datasources don't result in a separate Document being created. - Use them when working with complex datasources, i.e., datasources - which are an aggregation of multiple datasources. The current way to - add a nested datasource is using the key "NESTED_DATASOURCE". Indyo - accepts an IndexDataSource object, a List of IndexDataSources, - or an IndexDataSource[] for this key. + Nested datasources don't result in a separate Document being created. + Use them when working with complex datasources, i.e., datasources + which are an aggregation of multiple datasources. The current way to + add a nested datasource is using the key "NESTED_DATASOURCE". Indyo + accepts an IndexDataSource object, a List of IndexDataSources, + or an IndexDataSource[] for this key.
- This document was shamelessly ripped from the extremely well-written - and well-organized - Torque - tutorial. Thanks Pete! + This document was shamelessly ripped from the extremely well-written + and well-organized + Torque + tutorial. Thanks Pete!