简单 CRUD 的 EJB 3 会话 Bean 设计
我正在编写一个应用程序,其唯一目的是执行 CRUD 操作以维护数据库中的记录。一些表/实体之间存在关系。我见过的创建会话 bean 的大多数示例都涉及与许多我没有的实体交互的复杂业务逻辑/操作。
由于我的应用程序非常基础,那么会话 bean 的最佳设计是什么?
我正在考虑为每个实体创建一个会话 bean,其中定义了 CRUD 方法。然后我想到将所有这些会话 bean 合并到一个会话 bean 中。然后我发现这篇博客文章很有趣,但我必须承认我并不理解所有内容(什么是 ServiceFacade?)。
我倾向于会话 bean/实体类,但想听到更有经验的意见。
谢谢。
哎呀,这是博客链接: http://www.adam-bien.com/滚筒/abien/entry/generic_crud_service_aka_dao
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.
Oops, here's the blog link: http://www.adam-bien.com/roller/abien/entry/generic_crud_service_aka_dao
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
不确定您在谈论什么博客条目 :) 但在您的特定情况1 中,我可能会使用单个会话 bean 实现类似以下的接口:
并且该 bean 如下所示:
请参阅还有
1 大多数应用程序不应直接向客户端公开原始 CRUD,而应将 CRUD 屏蔽在实现业务规则和封装对域的访问的服务后面商店(
EntityManager
)。Not sure what blog entry you're talking about :) But in your particular situation1, I'd probably use a single session bean implementing an interface similar to:
And the bean would be as follow:
See also
1 Most application shouldn't expose raw CRUD directly to clients but shield CRUD behind services implementing business rules and encapsulating access to Domain Stores (the
EntityManager
).