Javatpoint Logo
Javatpoint Logo

Table Per Concrete class using xml file

In case of Table Per Concrete class, there will be three tables in the database having no relations to each other. There are two ways to map the table with table per concrete class strategy.

  • By union-subclass element
  • By Self creating the table for each class

Let's understand what hierarchy we are going to map.

table per concrete class

Let's see how can we map this hierarchy by union-subclass element:

In case of table per concrete class, there will be three tables in the database, each representing a particular class.
The union-subclass subelement of class, specifies the subclass. It adds the columns of parent table into this table. In other words, it is working as a union.

The table structure for each table will be as follows:

Table structure for Employee class

table per concrete class

Table structure for Regular_Employee class

table per concrete class

Table structure for Contract_Employee class

table per concrete class

Example of Table per concrete class

In this example we are creating the three classes and provide mapping of these classes in the employee.hbm.xml file.

1) Create the Persistent classes

You need to create the persistent classes representing the inheritance. Let's create the three classes for the above hierarchy:


2) Create the mapping file for Persistent class

The mapping has been discussed above for the hierarchy.

File: employee.hbm.xml

3) Add mapping of hbm file in configuration file

Open the hibernate.cgf.xml file, and add an entry of mapping resource like this:

Now the configuration file will look like this:

File: hibernate.cfg.xml

The property is defined for creating automatic table in the database.

4) Create the class that stores the persistent object

In this class, we are simply storing the employee objects in the database.


Please Share

facebook twitter google plus pinterest tumbler

Latest 4 Tutorials