-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: composite-id identifier properties approach (first approach)
PostPosted: Mon Oct 18, 2010 9:53 am 
Newbie

Joined: Mon Oct 18, 2010 9:35 am
Posts: 10
Hi to all,

I would like someone to elaborate me on the first approach for composite-id:
Quote:
Unfortunately, this approach to composite identifiers means that a persistent object is its own identifier. There is no convenient "handle" other than the object itself. You must instantiate an instance of the persistent class itself and populate its identifier properties before you can load() the persistent state associated with a composite key. We call this approach an embedded composite identifier, and discourage it for serious applications.

You can find this on the 1.5.6. composite-id chapter (Hibernate 3.2.) here.

I don't understand what is the difference with the third approach (where we specify a component composite object). In both cases there will be a object instantiation for identifying, right?! What does Hibernate in the third approach opposite to the first one?! Why is it so inappropriate?

Kind Regards,
despot


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.