[hibernate-commits] Hibernate SVN: r19991 - core/trunk/documentation/manual/src/main/docbook/en-US/content.

[hibernate-commits at lists.jboss.org]

Author: steve.ebersole at jboss.com
Date: 2010-07-21 02:00:52 -0400 (Wed, 21 Jul 2010)
New Revision: 19991

Modified:
   core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml
Log:
HHH-5397 - Odds and ends from documentation merge : fixed <programlisting/> rendering issue


Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml
===================================================================
--- core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml	2010-07-21 05:45:11 UTC (rev 19990)
+++ core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml	2010-07-21 06:00:52 UTC (rev 19991)
@@ -78,7 +78,10 @@
             Starting with version 3.3, Hibernate has a fare more powerful way to automatically determine
             which dialect to should be used by relying on a series of delegates which implement the
             <interfacename>org.hibernate.dialect.resolver.DialectResolver</interfacename> which defines only a
-            single method:<programlisting role="JAVA"><![CDATA[public Dialect resolveDialect(DatabaseMetaData metaData) throws JDBCConnectionException]]></programlisting>.
+            single method:
+        </para>
+        <programlisting role="JAVA"><![CDATA[public Dialect resolveDialect(DatabaseMetaData metaData) throws JDBCConnectionException]]></programlisting>
+        <para>
             The basic contract here is that if the resolver 'understands' the given database metadata then
             it returns the corresponding Dialect; if not it returns null and the process continues to the next
             resolver.  The signature also identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</exceptionname>