-->
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: Component class as Composite id - should it be persitent???
PostPosted: Wed Nov 24, 2004 8:28 am 
Newbie

Joined: Sun Nov 21, 2004 6:20 pm
Posts: 11
A simple question which is related to my previous question:

When you use a component class to wrap a composite-id in a table (see Reference 7.4)....must this component class be persisent or in other words...do I have to write a mapping-file for it?? Because actually I do not want to have it to be persistent, but as you can read in my previous question I have troubles with modelling associations to the class that has the composite-id which is wrapped in the component class....

THANX for any help....


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.