Is there something similar to Nhibernate "Mapping by code" for Hibernate

Question

In Nhibernate we have Fluent Nhibernate and, now, the built-in "Mapping by code" feature in Nhibernate 3.2. Both allow you to programmatically construct the mappings for your Domain and we could either write some conventions to map all the domain or we could write individual classes for each corresponding domain object.

Anything similar for Hibernate?

PepperBob · Accepted Answer · 2012-04-11 18:30:03Z

1

You should be able to configure Hibernate without XML and Annotations by using the Hibernate Configuration API, see http://docs.jboss.org/hibernate/orm/4.1/javadocs/org/hibernate/cfg/Configuration.html

Table mappings can be created through the Mappings API: http://docs.jboss.org/hibernate/orm/4.1/javadocs/org/hibernate/cfg/Mappings.html

I've never used the latter one as I found annotations the best way to go - but maybe the pointer helps.

answered Apr 11, 2012 at 18:30

PepperBob

7073 silver badges9 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Sleiman Jneidi · Accepted Answer · 2012-04-01 23:32:34Z

0

Yes, mapping by annotations, check this link

answered Apr 1, 2012 at 23:32

Sleiman Jneidi

23.4k14 gold badges60 silver badges80 bronze badges

5 Comments

Newbie Over a year ago

Correct me if wrong, there is no convention over configuration approach via annotations right? Meaning, I still need to litter all my classes with annotations one way or another.

Diego Mijelshon Over a year ago

How is that similar to mapping by code? It's equivalent to NHibernate.Mapping.Attributes

barsju Over a year ago

@newbie you are wrong. Hibernate has a pretty strong convention over configuration. You need a few annotations, but I would gladly argue that an entity class with some annotations looks "better" then the examples I have seen mapping in code. Mostly because you have your mapping code precisely where I need it.. But I don't expect everyone to agree.

João Mendes Over a year ago

The problem with annotations is that your domain classes now need to be persistence-aware. It's not a capital sin, but it's bad separation of concerns. Also, it doesn't answer the question.

rekiem87 Over a year ago

@joão-mendes If you have a good separation of concerns, you will have you entity classes and several domain classes, if you are using your Entity Tables as business models you do not have a good separation of concerns. A simple catalog when is added it just need a name, for edit also the id and maybe a status field, so, the entity is not suitable for both representations, the best is to have your repo layer and above them your business objects

Collectives™ on Stack Overflow

Is there something similar to Nhibernate "Mapping by code" for Hibernate

2 Answers 2

Comments

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related