From hibernate-commits at lists.jboss.org Thu May 29 07:44:14 2008
Content-Type: multipart/mixed; boundary="===============3129523863462293765=="
MIME-Version: 1.0
From: hibernate-commits at lists.jboss.org
To: hibernate-commits at lists.jboss.org
Subject: [hibernate-commits] Hibernate SVN: r14705 -
 search/trunk/doc/reference/en/modules.
Date: Thu, 29 May 2008 07:44:14 -0400
Message-ID: <E1K1gYI-0005mz-4o@committer01.frg.pub.inap.atl.jboss.com>

--===============3129523863462293765==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: hardy.ferentschik
Date: 2008-05-29 07:44:13 -0400 (Thu, 29 May 2008)
New Revision: 14705

Modified:
   search/trunk/doc/reference/en/modules/mapping.xml
Log:
HSEARCH-198 Updated the documentation regarding the term vector configurati=
on

Modified: search/trunk/doc/reference/en/modules/mapping.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- search/trunk/doc/reference/en/modules/mapping.xml	2008-05-29 11:27:38 U=
TC (rev 14704)
+++ search/trunk/doc/reference/en/modules/mapping.xml	2008-05-29 11:44:13 U=
TC (rev 14705)
@@ -4,9 +4,10 @@
   <title>Mapping entities to the index structure</title>
 =

   <para>All the metadata information needed to index entities is described
-  through some Java annotations. There is no need for xml mapping files no=
r a
-  list of indexed entities. The list is discovered at startup time scanning
-  the Hibernate mapped entities.</para>
+  through some Java annotations. There is no need for xml mapping files (in
+  fact there exists currently no xml configuration option) nor a list of
+  indexed entities. The list is discovered at startup time scanning the
+  Hibernate mapped entities.</para>
 =

   <section id=3D"search-mapping-entity" revision=3D"3">
     <title>Mapping an entity</title>
@@ -70,14 +71,12 @@
           <literal>Index.NO_NORM</literal> (do not store the normalization
           data). The default value is <literal>TOKENIZED</literal>.</para>
         </listitem>
-      </itemizedlist>
 =

-      <itemizedlist>
         <listitem>
-          <para>termVector: describes collections of term-frequency pairs.=
 To
-          utilize Term Vectors this attribute enables their being stored
-          during indexing so they are stored with documents. The default v=
alue
-          is Field.TermVector.NO.</para>
+          <para>termVector: describes collections of term-frequency pairs.
+          This attribute enables term vectors being stored during indexing=
 so
+          they are available within documents. The default value is
+          TermVector.NO.</para>
 =

           <para>The different values of this attribute are</para>
 =

@@ -95,7 +94,7 @@
 =

               <tbody>
                 <row>
-                  <entry align=3D"left">Field.TermVector.YES</entry>
+                  <entry align=3D"left">TermVector.YES</entry>
 =

                   <entry>Store the term vectors of each document. This
                   produces two synchronized arrays, one contains document
@@ -103,32 +102,32 @@
                 </row>
 =

                 <row>
-                  <entry align=3D"left">Field.TermVector.NO</entry>
+                  <entry align=3D"left">TermVector.NO</entry>
 =

                   <entry>Do not store term vectors.</entry>
                 </row>
 =

                 <row>
-                  <entry align=3D"left">Field.TermVector.WITH_OFFSETS</ent=
ry>
+                  <entry align=3D"left">TermVector.WITH_OFFSETS</entry>
 =

                   <entry>Store the term vector and token offset informatio=
n.
-                  This is the same as Field.TermVector.YES plus this conta=
ins
-                  the starting and ending offset position information for =
the
-                  terms</entry>
+                  This is the same as TermVector.YES plus it contains the
+                  starting and ending offset position information for the
+                  terms.</entry>
                 </row>
 =

                 <row>
-                  <entry align=3D"left">Field.TermVector.WITH_POSITIONS</e=
ntry>
+                  <entry align=3D"left">TermVector.WITH_POSITIONS</entry>
 =

                   <entry>Store the term vector and token position informat=
ion.
-                  This is the same as Field.TermVector.YES plus this conta=
ins
-                  the ordinal positions of each occurrence of a term in a
+                  This is the same as TermVector.YES plus it contains the
+                  ordinal positions of each occurrence of a term in a
                   document.</entry>
                 </row>
 =

                 <row>
                   <entry
-                  align=3D"left">Field.TermVector.WITH_POSITIONS_OFFSETS</=
entry>
+                  align=3D"left">TermVector.WITH_POSITIONS_OFFSETS</entry>
 =

                   <entry>Store the term vector, token position and offset
                   information. This is a combination of the YES, WITH_OFFS=
ETS


--===============3129523863462293765==--