JIT

<< 良好定义的service层应该这样。。。 | 首页 | Using HIbernate 3 as JDBC framework >> 2004-09-08 J2EE without EJB 读书笔记(chapter 3) Tag: Java技术文章 版权声明 :转载时请以超链接形式标明文章原始出处和作者信息及 本声明 http://jit.blogbus.com/logs/376318.html If possible, design applications to use a stateless service layer. Hold state in the web tier, rather than in the business logic tier, if possible. Do not put business logic in the web tier, in Struts Actions, or the like. Business logic should be independent of presentation. Essentially, a lightweight container will: ❑ Manage the lifecycle of business objects. A key distinction from an EJB container is that a lightweight container can manage POJOs: There is no need to implement special contracts, as with EJB. ❑ Provide a lookup facility, resolving dependencies managed objects may have on collaborators also managed by the lightweight container. Implementing Inversion of Control (IoC) is a key responsibility of a lightweight container. ❑ Ideally, provide enterprise services such as declarative transaction management to objects running within it, thus replacing a key value proposition of EJB. This is usually achieved using AOP. 随机文章: Enum example of Java 2004-11-23 良好定义的service层应该这样。。。 2004-09-08 我眼中的J2EE 2004-09-03 为hibernate生成建表文件 2004-05-27 在 Java 应用程序中计划重复执行的任务 2004-05-27 收藏到: Del.icio.us 引用地址: 发表于 10:41 | 编辑 | 继续话题 | 转发 | 推荐 发表评论

原始快照:web.archive.org