[hibernate-commits] Hibernate SVN: r14927 - search/trunk/doc/reference/en/modules.

[hibernate-commits at lists.jboss.org]

Author: hardy.ferentschik
Date: 2008-07-14 12:11:15 -0400 (Mon, 14 Jul 2008)
New Revision: 14927

Modified:
   search/trunk/doc/reference/en/modules/query.xml
Log:
HSEARCH-179:
Made it explicit that filter definitions are global.

Modified: search/trunk/doc/reference/en/modules/query.xml
===================================================================
--- search/trunk/doc/reference/en/modules/query.xml	2008-07-14 13:41:14 UTC (rev 14926)
+++ search/trunk/doc/reference/en/modules/query.xml	2008-07-14 16:11:15 UTC (rev 14927)
@@ -407,9 +407,11 @@
     <para>Declaring filters is done through the
     <classname>@FullTextFilterDef</classname> annotation. This annotation can
     be on any <literal>@Indexed</literal> entity regardless of the query the
-    filter is later applied to. Filter names must be unique since all filters
-    are globally visible. Each named filter has to point to an actual filter
-    implementation.</para>
+    filter is later applied to. This means filter definitions are global and
+    their names must be unique. A <classname>SearchException</classname> is
+    thrown in case two different <classname>@FullTextFilterDef</classname>
+    annotations with the same name are defined. Each named filter has to point
+    to an actual filter implementation.</para>
 
     <programlisting>@Entity
 @Indexed
@@ -540,7 +542,7 @@
     <classname>CachingWrapperFilter.</classname> The wrapper will cache the
     <classname>BitSet</classname> returned from the
     <methodname>bits(IndexReader reader)</methodname>method to avoid expensive
-    recomputation. </para>
+    recomputation.</para>
 
     <para>Hibernate Search also takes care of this aspect of caching. If the
     <literal>cache</literal> flag of <classname>@FullTextFilterDef