EJB 3 Session Bean Design for Simple CRUD
- by sdoca
I am writing an application that's sole purpose in life is to do CRUD operations for maintaining records in database. There are relationships between some of the tables/entities. Most examples I've seen for creating session beans deals with complex business logic/operations that interact with many entities which I don't have.
Since my application is so very basic, what would be the best design for the session bean(s)?
I was thinking of having one session bean per entity which had CRUD the methods defined. Then I thought of combining all of those session beans into a single session bean. And then I found this blog entry which is intriguing, but I must admit I don't understand all of it (what is a ServiceFacade?).
I'm leaning towards session bean/entity class, but would like to hear more experienced opinions.
Thanks.