• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EJB3 CRUD operations design question

 
Pieter-Jan Malfait
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic