EJB 3.0 Persistence is hot and coming. The fact that persistence is handled the same way, in and outside the EJB container, for Web Applications, Java Client applications and Distributed EJB based applications alike and by all major Object Relational Mapping frameworks – such as TopLink, Hibernate and KODO – will prove a compelling argument for many to start using the EJB 3.0 Persistence API as soon as it is finalized and production implementations are available. I have written several posts on this weblog on various aspects of EJB 3.0 Persistence. And I will write some more. In the mean time, I have written a pretty extensive article, introducing EJB 3.0 Persistence to an as yet uninformed audience. It provides some history, background and examples of Annotations, Data Manipulation and use of the EJB QL. Unfortunately for some, it is all in Dutch: EJB 3.0 Persistence – Nieuwe Industriestandaard voor Java/Database communicatie
see Oracle JDeveloper forum post
“SOD for ADF BC related to EJB 3.0”
http://forums.oracle.com/forums/thread.jspa?threadID=373341
Doug Clarke write an interesting article on choosing an ORM solution in JavaPro. The most interesting part to me is the table of aspects to consider when choosing an ORM approach; See http://www.ftponline.com/javapro/2004_12/online/dclarke_12_22_04/table1.aspx