Mapping file strategy

Chapter 4 Generating Hibernate Persistent Objects and JSF Pages

Mapping file strategy

Hibernate uses mapping files to define the mapping metadata. Each mapping file can contain metadata for one or many classes. PowerAMC uses the following grouping strategy:

A separate mapping file is generated for each single entity class that is not in an inheritance hierarchy.
A separate mapping file is generated for each inheritance hierarchy that has a unique mapping strategy. All mappings of subclasses are defined in the mapping file. The mapping file is generated for the root class of the hierarchy. See "Defining Hibernate Inheritance Mappings" for details about how the mapping strategy is determined.
No mapping file is generated for a single value type class that is not in an inheritance hierarchy. Its mapping is defined in its owner's mapping file.