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
This commit is contained in:
parent
c9412d06b9
commit
40ca8fe193
|
@ -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[
|
||||
|
|
Loading…
Reference in New Issue