Product Description

Persistence-the ability of data to outlive an instance of a program-is central to modern applications. Hibernate, the most popular Java persistence tool, provides automatic and transparent object/relational mapping making it a snap to work with SQL databases in Java applications. Hibernate applications are cheaper, more portable, and more resilient to change. Because it conforms to the new EJB 3.0 and Java Persistence 1.0 standard, Hibernate allows the developer to seamlessly create efficient, scalable Java EE applications.

Java Persistence with Hibernate explores Hibernate by developing an application that ties together hundreds of individual examples. You'll immediately dig into the rich programming model of Hibernate 3.2 and Java Persistence, working through queries, fetching strategies, caching, transactions, conversations, and more. You'll also appreciate the well-illustrated discussion of best practices in database design, object/relational mapping, and optimization techniques.

In this revised edition of the bestselling Hibernate in Action, authors Christian Bauer and Gavin King-the founder of the Hibernate project-cover Hibernate 3.2 in detail along with the EJB 3.0 and Java Persistence standard.

Product Details

• Amazon Sales Rank: #24044 in Books
• Published on: 2006-12-05
• Original language: English
• Number of items: 1
• Binding: Paperback
• 841 pages

About the Author
Christian Bauer is a member of the Hibernate developer team. He works as a trainer, consultant, and product manager for Hibernate, EJB 3.0, and JBoss Team at JBoss, a division of Red Hat. He is the co-author with Gavin King of Manning's best-selling Hibernate in Action.

Gavin King is the founder of the Hibernate project, and a member of the EJB 3.0 (JSR 220) expert group. He also leads the Web Beans JSR 299, a standardization effort involving Hibernate concepts, JSF, and EJB 3.0. Gavin King works as a lead developer as JBoss, a division of Red Hat.

Customer Reviews

Could have been so much better
I have found Hibernate In Action to be an indispensible guide when developing Hibernate persistence solutions, so I was eagerly awaiting the release of its successor.

Most developers will want to use standard JPA as much as possible for portability reasons, and only use Hibernate where absolutely necessary to use features not supported by JPA.
However this book fails to cleanly separate discussion of JPA from Hibernate, meaning that if you take this approach to using JPA you end up wading through large sections of the 800+ pages of this weighty tome.

I have to agree with Ganeshji and C. Updike - this lack of any clean separation of JPA and Hibernate makes it difficult to get useful information out of the book.

This is a shame, as the writing is of a high standard - unfortunately the content is very poorly organised.

Good book, but...
I read this book after reading Hibernate in Action, I found almost 70% of it repeated. So im not sure wether this book is value for money for me anyway. But if your starting out in hibernate I would probably say buy this, However if you already have Hibernate in Action, its not worth the extra cost and most of the information can be found on the net after some hunting.

Too much.
I've recently been reading Java Persistence with Hibernate, having had limited experience with Hibernate previously. My thinking was that a book this size should provide a really gentle but complete coverage.

After 5 months, I had got as far as Chapter 7. Normally, I fly through books, but there was something about this one that just didn't work for me. I don't like 'giving up', but by chapter 7 I asked myself honestly a) was I enjoying it and b) was I learning, and I came to 'no' for both.

The book (as we know) was written by the authors of Hibernate, and to this end they know it inside out. However, this is also their weakness. Instead of giving me what I needed - an overview, followed by some good examples that I could follow and learn from, they would show me one way to do something in Hibernate, then in annotations, then with JPA xml, then with JPA annotations except for the bits that couldn't be reached and so had to use Hibernate annotations. Then they would give me a reason/situation when this approach couldn't be used, and the process would start over with a new technique. As a reference, this is excellent. As a learning book, it's a nightmare, so much so that I've stopped reading.