aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes EJB3 CRUD operations design question Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "EJB3 CRUD operations design question" Watch "EJB3 CRUD operations design question" New topic
Author

EJB3 CRUD operations design question

Pieter-Jan Malfait
Greenhorn

Joined: Aug 23, 2005
Posts: 26
Would i be a good design choice to use a access point for the client in the from of a Session bean to manage CRUD operations for all EntityBeans in the application? All my entities inherit from the same Embedable superclass (which holds audit fields), so i could make just one Session bean that can persist, delete or retrieve any kind of Entity, instead of creating several session beans to handle each group of entities..

would this be a good design choice? i don't see much problems , but i didn't see this strategy anywhere else neither.. is there something i'm overlooking?
Pieter-Jan Malfait
Greenhorn

Joined: Aug 23, 2005
Posts: 26
didn't anyone encounter this problem already ? or is nobody using EJB3 yet in here ? maybe there is another forum with more active EJB3 users ?

thx
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: EJB3 CRUD operations design question