Author: mmcallis Date: 2008-02-05 21:43:45 -0500 (Tue, 05 Feb 2008) New Revision: 9793 Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml Log: updating/revising, adding another example to: 3.3.1. Database Dialect Settings for JBoss Portal Modified: docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml =================================================================== --- docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-06 02:37:14 UTC (rev 9792) +++ docs/branches/JBoss_Portal_Branch_2_6/referenceGuide/en/modules/configuration.xml 2008-02-06 02:43:45 UTC (rev 9793) @@ -140,27 +140,40 @@ </para> </sect1> <sect1 id="configuration-hibdialect"> - <title>Forcing the DB dialect</title> - <para>If you encounter that the Hibernate dialect is not working properly and would like to - override the default behavior, follow the instructions contained in this section: - <note>Under most common circumstances, the auto-detect feature should work fine.</note> + <title>Forcing the Database Dialect</title> + <para> + This sections describes how to override the Database (DB) dialect settings. Under most circumstances, the auto-detect feature will work. If the Hibernate dialect is not working correctly, override the default behavior by following the instructions in this section. </para> <sect2> - <title>DB Dialect settings for Portal</title> - <para>You will need to modify all the <literal>hibernate.cfg.xml</literal> files in all the Portal modules you - intend to use by uncommenting the following line in these files and using the appropriate dialect (see - <ulink url="http://www.hibernate.org/hib_docs/v3/reference/en/html/session-... - </ulink> for a list of supported dialects in Hibernate 3): - <programlisting><![CDATA[ + <title>Database Dialect Settings for JBoss Portal</title> + <para> + All <filename>hibernate.cfg.xml</filename> files in all JBoss Portal modules you intend to use need to be modified. The <filename>hibernate.cfg.xml</filename> files are found in the <filename>jboss-portal.sar/<replaceable>module</replaceable>/conf/hibernate/<replaceable>directory</replaceable>/</filename> directory, where <replaceable>module</replaceable> is the module name, and <replaceable>directory</replaceable> is a directory that, depending on the module, may or may not exist. + </para> + <para> + To modify these files to force the DB dialect, un-comment the following line from each <filename>hibernate.cfg.xml</filename> file in each JBoss Portal module you intend to use: + </para> + <para> +<screen><![CDATA[ <!-- Force the dialect instead of using autodetection --> <!-- <property name="dialect">org.hibernate.dialect.PostgreSQLDialect</property> --->]]></programlisting> - </para> - <para>These files are found in <literal>jboss-portal.sar/[module]/conf/hibernate/[directory]/hibernate.cfg.xml</literal> - where <literal>[module]</literal> is a module name and <literal>[directory]</literal> is a directory that - may or may not be present. - </para> +--> +]]> +</screen> + </para> + <para> + After un-commenting, the <filename>hibernate.cfg.xml</filename> will look as follows: + </para> + <para> +<screen><![CDATA[ +<!-- Force the dialect instead of using autodetection --> +<property name="dialect">org.hibernate.dialect.PostgreSQLDialect</property> +]]> +</screen> + </para> + <para> + Note: these examples are for a PostgreSQL database. If you use another database, you will need to modify <computeroutput>org.hibernate.dialect.PostgreSQLDialect</computeroutput> to reflect the correct database. + </para> </sect2> <sect2> <title>DB Dialect settings for the CMS component</title>