Priority when co-existing Annot., orm.xml and hbm.xml?

pstein · **Joined:** Wed Oct 08, 2008 10:59 am **Posts:** 37

Assume I use JPA with Hibernate as implementation.

Accidentially or intentionally in my project there are
- Annotations in Java source
- orm.xml
and
- xxxx.hbm.xml
config files.

With contradicting mappings.

Which one has priority?

Can they co-exist at all or will there be an error (at runtime)?

Can I define a different priority hierarchy (If yes: How?) ?

Peter

hallmit · **Posted:** Thu Dec 16, 2010 5:21 am

according to hibernate doc [1]

Quote:

You can mix annotated persistent classes and classic hbm.cfg.xml declarations with the same SessionFactory. You can however not declare a class several times (whether annotated or through hbm.xml). You cannot mix configuration strategies (hbm vs annotations) in an entity hierarchy either.

Quote:

To ease the migration process from hbm files to annotations, the configuration mechanism detects the mapping duplication between annotations and hbm files. HBM files are then prioritized over annotated metadata on a class to class basis. You can change the priority using hibernate.mapping.precedence property. The default is hbm, class, changing it to class, hbm will prioritize the annotated classes over hbm files when a conflict occurs.

[1] http://docs.jboss.org/hibernate/stable/ ... ml_single/