Hi, Is inheritance mapping based following db pattern supported in hibernate? Please note that subclass table TBL_USER has it's own primary key, which is different from the one in "table per subclass" strategy.

Table TBL_PERSON
(
ID INT NOT NULL,
FIRST_NAME VARCHAR(50),
LAST_NAME VARCHAR(50),
PRIMARY KEY (ID)
)

Table TBL_USER
(
ID INT NOT NULL,
PERSON_ID INT NOT NULL,
USERNAME VARCHAR(50),
PASSWORD VARCHAR(50),
PRIMARY KEY (ID),
FOREIGN KEY (PERSON_ID) REFERENCES TBL_PERSON(ID)
)

Thank you.

No.
This kind of relation is a many-to-one and Hibernate cannot transform it into a class hierarchy

Does it matter if PERSON_ID in TBL_PERSON is a UNIQUE constraint?
Thank you.

Consider a one-to-one composition relationship between Person and UserAccount. You should favor Composition over Inheritance in OOP.

Yes, but composition doesn't replace inheritance and Person and User here are just examples.

PERSON_ID in TBL_USER? being unique would make it one-to-one.

Well it won't be enough for Hibernate.

Thanks to all! I changed the code to adopt "table per subclass" strategy

You must have missed classes on OOP Analysis and Design. "Is a" implies inheritance. "Has a" implies composition.
The argument that composition should be favored over inheritance is more against inappropriate use of inheritance rather than saying that composition should be used in place of inheritance.