I am using the ant task and would like to know how to make it generate the pojo with a composite key without a secondary id class
what setting do i change

PS SO far i like using the tools

you mean you want embedded composite id's inside your mappings ?

We do not recommend that at all when using the core (unless you really have to) and we don't support generation of that in the tools (and noone asked for it before...sooo you will have to come up with a good reason ;)

http://www.hibernate.org/hib_docs/v3/re ... ompositeid

seems to set up some reasons for imbedded composite-keys.

If i am on drugs could you point me to using them as seperate classes?

and why does most of the documentation use imbedded ones.

and doesn't the use of seperate classes cause foreign key issues?

Yes we have the worse kind of legacy db ... non tech people designed it and the imbedded compsite keys so far have handled everthing.

I also have 40+ imbedded keys .... won't i have to change these?

is there a rpo/con list to both approaches?

PS I am not arguing just panicing that I change and then find out I can no longer support our data model

THanks for your reponse

huh ? it only shows external composite-keys.



the docs you just pointed me to.



huh ? no it does not. most of the docs uses single column/field id's. (not composite!)



huh!?



maybe you should tell me what you mean by "imbedded composite keys".



depends what you actually mean.

Hibernate supports composite ids perfectly fine and these keys will of course be "embedded" into the same table as the data.....but in the object model it is much nicer to have the id encapsulated in its own class instead of being "flattend" out onto the entity.



read about it here: http://www.hibernate.org/hib_docs/v3/re ... ompositeid



don't worry. hibernate supports more than what the tools generate...we just don't like to generate something we don't recommend people to do.

And embedded composite-ids into the domain model is not recommended.

WHy is it not recommended?
And will usingh the external key class hurt setting up foreign key relatinships based only on part of the primary key?

and thanks for quick response it helps alot

if you had read the part in the docs i pointed you would see it points out all the problems with it.



I have no idea why you say this. external key class does not affect your table layout in any way.