From 40ca8fe1933545779389badba1cc1849167c9f5b Mon Sep 17 00:00:00 2001
From: Max Rydahl Andersen <max@hibernate.org>
Date: Sun, 19 Dec 2004 22:01:25 +0000
Subject: [PATCH] Fixes HB-60

ordering of hbm.xml is now not required when using extends.


git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@5011 1b8cb986-b30d-0410-93ca-fae66ebed9b2
---
 reference/en/modules/basic_mapping.xml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/reference/en/modules/basic_mapping.xml b/reference/en/modules/basic_mapping.xml
index 8a20fab737..03eb9b1f55 100644
--- a/reference/en/modules/basic_mapping.xml
+++ b/reference/en/modules/basic_mapping.xml
@@ -2448,14 +2448,16 @@
 
     </sect1>
 
-   <sect1 id="mapping-modularfiles">
+   <sect1 id="mapping-modularfiles" revision="2">
        <title>Modular mapping files</title>
        <para>
             It is possible to define <literal>subclass</literal> and <literal>joined-subclass</literal>
             mappings in seperate mapping documents, directly beneath <literal>hibernate-mapping</literal>.
             This allows you to extend a class hierachy just by adding a new mapping file. You must
             specify an <literal>extends</literal> attribute in the subclass mapping, naming a previously
-            mapped superclass. Use of this feature makes the ordering of the mapping documents important!
+            mapped superclass. Note: Previously this feature made the ordering of the mapping documents important. Since Hibernate 3, the
+            ordering of mapping files does not matter when using the extends keyword. The ordering inside a single mapping file
+            still needs to be defined as superclasses before subclasses.
         </para>
     
         <programlisting><![CDATA[