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
Introduction to EJB 3.0 Persistence – article in Dutch
Related Posts
About The Author
Lucas Jellema
Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director and Oracle Developer Champion. Solution architect and developer on diverse areas including SQL, JavaScript, Kubernetes & Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press book Oracle SOA Suite 12c Handbook. Frequent presenter on user groups and community events and conferences such as JavaOne, Oracle Code, CodeOne, NLJUG JFall and Oracle OpenWorld.
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