Hi!

Here is my problem:

I've two eclipse projects; the first contains abstract entities, that will be used in multiply projects. The second is my current project, which contains the first as a reference, so i can use those abstract entities in a production application.

I'm using the table per subclass inheritance strategy, to map my entities to database. The problem with this solution is that i have to map my inheritance hierarchies in one hbm.xml.
There are inheritance hierarchies which starts in my first project, and ends in my second. Mapping files are located in my abstract project, so it contains information about my current project, but it should not do.

Thanks for any help.

up

If I understand you correctly, you are trying to avoid references from the abstract project to the concrete project and use the table per subclass inheritance mapping.

According to the Hibernate docs you should be able to have separate mapping files for your subclasses that use <joined-subclass> as a top level element (i.e. instead of class). These can reside in your concrete project. They will need to specify the class that they extend of course since they are not lexically inside a class definition.

I did this using <subclass> for the table per class hierarchy strategy.

Good luck.

Thanks, it works.

Can you point me to the place in the docs? I would like to map class per table and I would have each class mapping in a separate file. I rather not nest the entire hierarchy in one file.

See section 5.1.14 in the pdf of the reference document. It's also in the book Hibernate in Action in section 3.6.4. It's quite straightforward. Just put your subclass mapping in a separate file and add the attribute 'extends' to it. E.g.