Hibernate Recipes: A Problem-Solution Approach

by Gary Mak, Srinivas Guruzu

Hibernate continues to be the most popular out-of-the-box framework solution for Java Persistence and data/database accessibility techniques and patterns. It is used for e-commerce–based web applications as well as heavy-duty transactional systems for the enterprise. Gary Mak , the author of the best-selling Spring Recipes , now brings you Hibernate Recipes . This book contains a collection of code recipes and templates for learning and building Hibernate solutions for you and your clients. This book is your pragmatic day-to-day reference and guide for doing all things involving Hibernate. There are many books focused on learning Hibernate, but this book takes you further and shows how you can apply it practically in your daily work.

Genres: Programming

333 pages, Paperback

First published June 29, 2010

Reviews

[Eve · Rating 3 out of 5]

I stepped out on a limb ordering this new book that doesn't have any reviews, mostly in order to get up to date information about the latest version of hibernate.

I'm an experienced Java developer, and until now I've largely written my own database layer, so I'm aware of the difficulties behind doing it. I've been meaning to check out hibernate for a while, and I finally had a project that would make good use of a framework (and that I was starting from scratch), so I decided to go for it.

First, let me say that I did get what I wanted from this book, meaning that it gave me some good ideas that I could immediately apply to the project I'm working on. For that I could have given it 5 stars.

In particular, I liked the several sections where they gave both the hbm.xml version and the annotation version of the mapping configuration for the solution code. To me, those sections were invaluable, giving me a greater understanding of how the annotation stuff works, and I'll probably end up using it on this project (converting what I have so far). It looks more maintainable.

However, the book has some issues.

I use checkstyle for any Java code I write, and I expect authors of books to at least use a formatter to format the code in a standard way before publication (and if they don't, to be extremely careful to be consistent). I subtract 2 stars largely because of the extremely poorly formatted/indented/spaced code examples (and there are a few typos in the code as well, that I could see just by reading through the examples). They switch between spaces and tabs, and have one line indented 40 spaces and the next line not indented at all, in the same block. I don't know how it got through editing stages in this state! I've seen much better looking "beta" books. To the authors: use checkstyle!