HHH-5149 fix text not wrapping up in html rendering

Was due to a itemizedlist embedded in a para

git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@19710 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Emmanuel Bernard 2010-06-10 16:20:43 +00:00
parent 1eaf80e3a9
commit 74a5e4b405
1 changed files with 31 additions and 29 deletions

View File

@ -2308,8 +2308,8 @@ class Person {
<listitem> <listitem>
<para><literal>optimizer</literal> (optional - defaults to <para><literal>optimizer</literal> (optional - defaults to
<literal></literal>): See <xref <literal>??</literal>): See <xref
linkend="mapping-declaration-id-enhanced-optimizers" /></para> linkend="mapping-declaration-id-enhanced-optimizers" />.</para>
</listitem> </listitem>
</itemizedlist></para> </itemizedlist></para>
@ -2323,35 +2323,37 @@ class Person {
exhausted your in-memory value group. This is the role of the exhausted your in-memory value group. This is the role of the
pluggable optimizers. Currently only the two enhanced generators pluggable optimizers. Currently only the two enhanced generators
(<xref linkend="mapping-declaration-id-enhanced" /> support this (<xref linkend="mapping-declaration-id-enhanced" /> support this
operation. <itemizedlist spacing="compact"> operation. </para>
<itemizedlist spacing="compact">
<listitem> <listitem>
<para><literal>none</literal> (generally this is the default <para><literal>none</literal> (generally this is the default if
if no optimizer was specified): this will not perform any no optimizer was specified): this will not perform any
optimizations and hit the database for each and every optimizations and hit the database for each and every
request.</para> request.</para>
</listitem> </listitem>
<listitem> <listitem>
<para><literal>hilo</literal>: applies a hi/lo algorithm <para><literal>hilo</literal>: applies a hi/lo algorithm around
around the database retrieved values. The values from the the database retrieved values. The values from the database for
database for this optimizer are expected to be sequential. The this optimizer are expected to be sequential. The values
values retrieved from the database structure for this retrieved from the database structure for this optimizer
optimizer indicates the "group number". The indicates the "group number". The
<literal>increment_size</literal> is multiplied by that value <literal>increment_size</literal> is multiplied by that value in
in memory to define a group "hi value".</para> memory to define a group "hi value".</para>
</listitem> </listitem>
<listitem> <listitem>
<para><literal>pooled</literal>: as with the case of <para><literal>pooled</literal>: as with the case of
<literal>hilo</literal>, this optimizer attempts to minimize <literal>hilo</literal>, this optimizer attempts to minimize the
the number of hits to the database. Here, however, we simply number of hits to the database. Here, however, we simply store
store the starting value for the "next group" into the the starting value for the "next group" into the database
database structure rather than a sequential value in structure rather than a sequential value in combination with an
combination with an in-memory grouping algorithm. Here, in-memory grouping algorithm. Here,
<literal>increment_size</literal> refers to the values coming <literal>increment_size</literal> refers to the values coming
from the database.</para> from the database.</para>
</listitem> </listitem>
</itemizedlist></para> </itemizedlist>
</section> </section>
</section> </section>