Author: epbernard
Date: 2010-08-23 13:50:55 -0400 (Mon, 23 Aug 2010)
New Revision: 20231
Modified:
search/trunk/hibernate-search/src/main/docbook/en-US/modules/configuration.xml
Log:
Fix illegal XML
Modified: search/trunk/hibernate-search/src/main/docbook/en-US/modules/configuration.xml
===================================================================
---
search/trunk/hibernate-search/src/main/docbook/en-US/modules/configuration.xml 2010-08-23
17:06:32 UTC (rev 20230)
+++
search/trunk/hibernate-search/src/main/docbook/en-US/modules/configuration.xml 2010-08-23
17:50:55 UTC (rev 20231)
@@ -1024,24 +1024,13 @@
</section>
<section id="search-configuration-directory-lockfactories"
revision="1">
-
-
<title>LockFactory configuration</title>
-
-
-
<para>Lucene Directories have default locking strategies which work well
for most cases, but it's possible to specify for each index managed by
Hibernate Search which LockingFactory you want to use.</para>
-
-
-
<para>Some of these locking strategies require a filesystem level lock and
may be used even on RAM based indexes, but this is not recommended and of
no practical use.</para>
-
-
-
<para>To select a locking factory, set the
<literal>hibernate.search.<index>.locking_strategy</literal>
option
to one of <literal>simple</literal>,
<literal>native</literal>,
@@ -1049,76 +1038,57 @@
fully qualified name of an implementation of
<literal>org.hibernate.search.store.LockFactoryFactory</literal>;
Implementing this interface you can provide a custom
- <literal>org.apache.lucene.store.LockFactory</literal>. <table
- id="search-configuration-directory-lockfactories-table">
+ <literal>org.apache.lucene.store.LockFactory</literal>.</para>
+ <table id="search-configuration-directory-lockfactories-table">
<title>List of available LockFactory implementations</title>
-
<tgroup cols="3">
<thead>
<row>
<entry align="center">name</entry>
-
<entry align="center">Class</entry>
-
<entry align="center">Description</entry>
</row>
</thead>
-
<tbody>
<row>
<entry>simple</entry>
-
<entry>org.apache.lucene.store.SimpleFSLockFactory</entry>
-
<entry>
<para>Safe implementation based on Java's File API, it marks
the usage of the index by creating a marker file.</para>
-
<para>If for some reason you had to kill your application, you
will need to remove this file before restarting it.</para>
-
<para>This is the default implementation for
<literal>FSDirectoryProvider</literal>,<literal>FSMasterDirectoryProvider</literal>
and
<literal>FSSlaveDirectoryProvider</literal>.</para>
</entry>
</row>
-
<row>
<entry>native</entry>
-
<entry>org.apache.lucene.store.NativeFSLockFactory</entry>
-
<entry>
<para>As does <literal>simple</literal> this also marks
the
usage of the index by creating a marker file, but this one is
using native OS file locks so that even if your application
crashes the locks will be cleaned up.</para>
-
<para>This implementation has known problems on NFS.</para>
</entry>
</row>
-
<row>
<entry>single</entry>
-
<entry>org.apache.lucene.store.SingleInstanceLockFactory</entry>
-
<entry>
<para>This LockFactory doesn't use a file marker but is a Java
object lock held in memory; therefore it's possible to use it
only when you are sure the index is not going to be shared by
any other process.</para>
-
<para>This is the default implementation for
<literal>RAMDirectoryProvider</literal>.</para>
</entry>
</row>
-
<row>
<entry>none</entry>
-
<entry>org.apache.lucene.store.NoLockFactory</entry>
-
<entry>
<para>All changes to this index are not coordinated by any
lock; test your application carefully and make sure you know
@@ -1127,19 +1097,12 @@
</row>
</tbody>
</tgroup>
- </table></para>
-
- Configuration example:
-
+ </table>
+ <para>
+ Configuration example:</para>
<programlisting>hibernate.search.default.locking_strategy simple
hibernate.search.Animals.locking_strategy native
hibernate.search.Books.locking_strategy
org.custom.components.MyLockingFactory</programlisting>
-
-
-
- <para />
-
-
</section>
<section>
Show replies by date