-->
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: Hibernate design mapping
PostPosted: Fri Nov 16, 2012 1:18 am 
Newbie

Joined: Fri Oct 14, 2005 7:52 am
Posts: 9
Location: delhi

Hi
I have been using hibernate since last 5 years .
The one problem that I have identified when we need to fetch/save object with one-to-many , many-to-many kind of mapping.
I am going to start a new application from scratch and need your valuable suggestion on design.

This time I am thinking NOT TO DEFINE any mapping in HBM file for objects and treat all objects individually .
For example There are 2 objects Employee & Addresses and one Employee can have multiple addresses .
Earlier we use to define one-to-many mapping between these 2 objects .

But in new design , no mapping to define.

Thanks to please let me know the pros & cons of this design .


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.