添加标题
添加标题
内容 C
内容 B
内容 A
关 系 图
A结点 D结点 C结点 B结点 A B C D 关系
概 念 图
概念C
概念D
概念B
概念A
项 目 图
XXXXXXXXXXXXXXXXXXXXXXXXXXX
A
01
A
B
02
YYYYYYYYYYYYYYYYYYYYYYYY
C
03
B C ZZZZZZZZZZZZZZZZZZZZZZZZZZ
样例文本B
样例文本C
EJB规范起初的一个主要价值—对分布式应用进行事务管理—在随后的实践中被一致认为几乎没能派上用场。对于企业级应用来说，Spring和Hibernate等简化框架更加实用。因此，EJB 3.0规范（JSR 220）为了迎合这个趋势相比于其前辈进行了一次激进的大跳跃。受到Spring 影响，EJB 3.0也使用所谓的“传统简单Java对象（POJO）”；同时，支持依赖注入来简化全异系统的集成与配置。Hibernate的创始人Gavin King参与了这一新版规范的制订，并对EJB大加提倡。Hibernate的许多特性也被引入到Java持久化API当中，从而取代原来的实体bean。EJB 3.0规范大幅采用Java注释（annotation）来对代码进行元数据修饰，从而消减了此前EJB编程的冗杂性。 相应地，EJB 3.0几乎成为了一个全新的API，与此前的数版可谓毫无相似度可言。
样例文本B
The vision was persuasively presented by EJB advocates such as IBM and Sun Microsystems, and Enterprise JavaBeans were quickly adopted by large companies. Problems were quick to appear, however, and the reputation of EJBs began to suffer as a result. Some developers felt that the APIs of the EJB standard were far more complex than those developers were used to. An abundance of checked exceptions, required interfaces, and the implementation of the bean class as an abstract class were all unusual and counter-intuitive for many programmers. The problems that the EJB standard was attempting to address, such as object-relational mapping and transactional integrity, were complex, however many programmers found the APIs to be just as difficult if not more so, leading to a widespread perception that EJBs introduced complexity without delivering real benefits.
