As Roland explains in "Examining the EJB 3.0 Simplified API specification," the EJB 3.0 spec consists of three parts:
- EJB 3.0 Simplified API
- Enterprise JavaBeans Core Contracts and Requirements
- Persistence API
The part that is creating the most interest and controversy is the persistence API, namely: How will entity beans work in EJB 3.0? Will they be JDOs? Will they be like Hibernate? Will they be backwards compatible with entity beans in EJB 2.1?
As Wayne has pointed out in his blog, Mike Keith has written a really interesting blog entry, The EJB 3.0 Hibernate Fallacy, which explains that the EJB 3.0 persistence model is its own animal, not just a copy of Hibernate, JDO, or TopLink. And Mike should know what he's talking about: He works at Oracle, is an architect for TopLink, and is on the EJB 3.0 committee. So if you'd like to learn some fact and not so much fiction, check out his blog.