I read some thing about how to mapping a composite key in the hibernate (against legacy db). It is recommended to seperate a composite key columns to a sperate class. Could you please provide what are advantages or disadvantages with this approach? -- or it is only way?

Thanks!
Ben



Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:


Problems with Session and transaction handling?

Read this: http://hibernate.org/42.html

What I've found when mapping composite keys to a separate class, is that it's much easier to load the class. I'm using Spring, so with the primary key of any hibernate mapping, I can just pass it off to the fetchById() method, and it will return the object I want.


However, it makes querying with the criteria api a bit trickier. If I recall correctly (and please let me know if I'm wrong) you have to create a criteria on the main class and then create a subcriteria on the composite key class to add your restrictions.


Anymore, I do more querying than fetching by id, so I don't abstract the composite key elements into a seperate class. That's my preference.

Hope this helps.