aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Good idea or not - 1 Entity Bean, multiple tables? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Good idea or not - 1 Entity Bean, multiple tables?" Watch "Good idea or not - 1 Entity Bean, multiple tables?" New topic
Author

Good idea or not - 1 Entity Bean, multiple tables?

Sheila Wallace
Greenhorn

Joined: May 24, 2001
Posts: 10
There have been a number of questions in this forum asking about mapping a single entity bean to multiple tables in a database. I know that this is possible and how to achieve it, however, I would like your opinion on whether this would ver be a good idea. In EJB 2.0, CMR means that we can effectively map 1 bean to 1 table and allow the container to manage the relationships. Can anyone think of a situation where this shouldn't be used and instead you should map 1 bean to multiple tables yourself?
Thanks for any thoughts on the matter.
Anselm Paulinus
Ranch Hand

Joined: Sep 05, 2003
Posts: 389
A case of join operations on tables
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Good idea or not - 1 Entity Bean, multiple tables?