Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Pro EJB 3: Java Persistence API Paperback – May 9, 2006
See the Best Books of 2017
Looking for something great to read? Browse our editors' picks for the best books of the year in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
From the reviews:
"An introduction to the new Java Persistence application programming interfaces (APIs), this book serves not only as a tutorial on how to use them, but also as a basic reference text. … The book is very well written, and the technical material is presented clearly without excessive detail. … this is an excellent textbook." (M. S. Joy, ACM Computing Reviews, Vol. 49 (3), March, 2008)
About the Author
Mike Keith wasthe co-specification lead for JPA 1.0 and a member of the JPA 2.0 and JPA 2.1expert groups. He sits on a number of other Java Community Process expertgroups and the Enterprise Expert Group (EEG) in the OSGi Alliance. He holds aMasters degree in Computer Science from Carleton University, and has over 20years experience in persistence and distributed systems research and practice.He has written papers and articles on JPA and spoken at numerous conferencesaround the world. He is employed as an architect at Oracle in Ottawa, Canada,and is married with four kids and two dogs.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Have been worked on EJB 2.x for many years and on several projects with different application servers (Weblogic, JBoss, WebSphere), I understand the basics of EJB. So I want not only understand the basic how-to in EJB3 and JPA, but also want to understand the in depth explanations on transaction, persistence context and different behavior in the new system.
The book explain all these topics very well. I had brought other book (hibernate in action with JPA pdf version), but found that book was too focused on hibernate (even I was a fan of the previous edition of hibernate in action book). This book is well focused on JPA,and I really likes JPA APIs.
The book author is really nice and accessible. I have emailed Mike questions and he consistently replied promptly.
This book worth the money !!!
I did augment reading with a lot of coding, but I was able to use this as my primary reference. The only place where I needed to use other resources was in the area of error handling in the JPA provider's implementation. This is clearly beyond the scope of the book and I do not blame the book for that.
If you are going to be using JPA in a JSE environment, be prepared to use this book to understand what you should do and use the source code of your JPA implementation to figure out what you must do.
I would highly recommend this book for anyone wanting to use the JPA spec.
My only comment about this book is that there are some typos and wrong references to figures and listings.
While this book is the definitive text for EJB3's Persistence API, it goes well beyond this and should become the standard text on object-relational persistence in general. For EJB developers this book will be essential, but even if you are maintaining or developing your own non EJB3-persistence solution, the insights offered by this book are invaluable. All the key issues surrounding enterprise object-relational persistence are described in detail, and the EJB3 solutions are explained clearly. If you want to understand what object-relational mapping is, this is the book.
Persistence is a complex problem that lies on the critical path to project success. This book explains how the new Java Persistence API in EJB3 solves this problem more simply (and more completely) than earlier versions of EJB. With "plain old Java objects" instead of cumbersome "components," design, development, and testing is radically simplified. But because of the nature of the o/r mapping problem, there is the potential for complexity - you are dealing not only with developing Java code, but also database schema, queries, XML mapping files, code-annotations, managing persistence-units, and all the deployment and runtime considerations that go along with application servers. However, even when things get difficult, there is now a success-path you can follow. This book does not gloss-over these details - through careful explanation it shows a path through them. At no point do you feel that this was written by technology evangelists intent on selling you on EJB 3, but instead by expert developers who want to show you how to use it to your advantage.
For those who have followed the development of the EJB spec, there are great (and for me, even entertaining) insights into the evolution of EJB's vision of persistence. Those who remember the clunky Entities of the early specifications will be shocked by the flexibility and power that the new approach provides. This book makes it clear that, for the 3.0 release, the EJB specification writers have taken the time to understand and solve many of the problems of persistence. The authors take the time to explain the approaches to the persistence problem that different versions of the EJB spec (and others, like JDO) have attempted, and shows rather convincingly that the new EJB3 Persistence API is firmly based on tested products and approaches from industry (like TopLink and Hibernate). EJB and o/r mapping are now mature, industry-ready technologies, and this book clearly explains how to understand and use them successfully.
Developers of enterprise applications should read this book to understand persistence issues and how to use EJB3 products (or adapt their own persistence frameworks) to address them. Managers should to read this book so they can make sure that their teams are aware of these issues and that their project plans take them into account. Sales engineers can use this book as a tool to educate their clients about how EJB3 products solve the object-model / relational-model "impedance mismatch."
A great book - many people should read it, and if they do, the quality of our software can only improve.