[hibernate-commits] Hibernate SVN: r11470 - trunk/HibernateExt/shards/doc/reference/en/modules.

[hibernate-commits at lists.jboss.org]

Author: max.ross
Date: 2007-05-06 17:47:18 -0400 (Sun, 06 May 2007)
New Revision: 11470

Modified:
   trunk/HibernateExt/shards/doc/reference/en/modules/configuration.xml
Log:
Fix doc bug http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-6
Config files are now referred to by consistent names.

Modified: trunk/HibernateExt/shards/doc/reference/en/modules/configuration.xml
===================================================================
--- trunk/HibernateExt/shards/doc/reference/en/modules/configuration.xml	2007-05-04 13:45:20 UTC (rev 11469)
+++ trunk/HibernateExt/shards/doc/reference/en/modules/configuration.xml	2007-05-06 21:47:18 UTC (rev 11470)
@@ -169,7 +169,7 @@
             shard-specific database url, database user, and database password, and that's all. This means that if you change the
             connection pool parameters in shard1.hibernate.cfg.xml, those parameters will be ignored. If you add another
             mapping file to the <classname>Configuration</classname>
-            loaded with the properties defined in weather2.hibernate.cfg.xml, that mapping will be ignored.
+            loaded with the properties defined in shard2.hibernate.cfg.xml, that mapping will be ignored.
             With the exception of the properties listed above, the configuration of our shard-aware
             <classname>SessionFactory</classname> comes entirely from the prototype
             <classname>Configuration</classname>. This may seem a bit strict, but the sharding code
@@ -202,7 +202,7 @@
             Now let's take a look at the configuration and mapping files that we loaded in. You'll definitely recognize
             them, but there are a few key additions and modifications related to sharding.
             <programlisting><![CDATA[
- 1    <!-- Contents of weather0.hibernate.cfg.xml -->
+ 1    <!-- Contents of shard0.hibernate.cfg.xml -->
  2    <hibernate-configuration>
  3      <session-factory name="HibernateSessionFactory0"> <!-- note the different name -->
  4        <property name="dialect">org.hibernate.dialect.MySQLInnoDBDialect</property>
@@ -216,7 +216,7 @@
  12  </hibernate-configuration>
                 ]]></programlisting>
             <programlisting><![CDATA[
- 1    <!-- Contents of weather1.hibernate.cfg.xml -->
+ 1    <!-- Contents of shard1.hibernate.cfg.xml -->
  2    <hibernate-configuration>
  3      <session-factory name="HibernateSessionFactory1"> <!-- note the different name -->
  4        <property name="dialect">org.hibernate.dialect.MySQLInnoDBDialect</property>
@@ -229,7 +229,7 @@
  11    </session-factory>
  12  </hibernate-configuration>
                 ]]></programlisting>
-            We'll skip the contents of weather2.hibernate.cfg.xml because the pattern should by now be obvious. We're
+            We'll skip the contents of shard2.hibernate.cfg.xml because the pattern should by now be obvious. We're
             giving each session factory a unique name via the name attribute of the session-factory element, and we're
             also giving each session factory a shard id. This is required. If you try to configure a
             <classname>ShardedSessionFactory</classname> with a <classname>Configuration</classname>