HHH-5397 - Odds and ends from documentation merge : fixed <programlisting/> rendering issue

git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@19991 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Steve Ebersole 2010-07-21 06:00:52 +00:00
parent 0303d88761
commit 48a5e04caa
1 changed files with 4 additions and 1 deletions

View File

@ -78,7 +78,10 @@
Starting with version 3.3, Hibernate has a fare more powerful way to automatically determine 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 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 <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 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 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> resolver. The signature also identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</exceptionname>