If Hibernate makes Java-based, data-persistence, so incredibly easy to perform, then why do all of the most popular resources make Hibernate technology so darned impossible to learn? Well, learning Hibernate doesn't have to be hard anymore; not with a copy of Hibernate Made Easy by your side!

Does Hibernate Really Have to be That Hard?

Cameron McKenzie's, Hibernate Made Easy, finally brings to light the idea that a technology that is fun and easy to use, should also be fun and easy to learn. Building upon simple, straight forward examples that make even the most difficult topics easy to understand, this book explores all of the key concepts that you absolutely must know in order to start effectively leveraging the Hibernate framework. Discarding the old, XML based, -hbm- mapping files, Hibernate Made Easy will show you how to simplify your designs by leveraging both Hibernate and JPA annotations together, making your applications more manageable, maintainable, and most importantly, faster and easier to develop.

Hibernate Made Easy: Friendly and Conversational

From the fundamental, Create, Retrieve, Update & Delete operations, to the mapping of complex inheritance hierarchies, Hibernate Made Easy explains it, using a friendly and conversational style that reads less like a technical book, and more like an informative and engaging conversation with a seasoned Hibernate expert.

From CRUD Operations to Advanced Data Access Objects

And while the examples in the book are incredibly easy to follow and reproduce (there are no code errors in this book - that's guaranteed!), the concepts this book will help you master will empower you to solve even the most daunting programming challenges. From managing transactions over an HTTP based, request-response cycle, to implementing highly advanced Data Access Objects (DAOs) with Java 's generics, this book will teach you what you really need to know about Java based persistence with Hibernate.

Hurry Up and Hibernate!

If you want to learn Hibernate, if you want to learn Hibernate quickly, and you want it explained in a manner that is easy to follow and understand, there really is no other choice. Get a copy of Cameron McKenzie's Hibernate Made Easy today!

The $100 Error Free Code Challenge

I really have no tolerance for programming books that contain errors in their code. I mean, how can someone learn if what they are being taught is wrong? There are a lot of reasons why technical books get riddled with code errors, but I don't find any of those excuses acceptable.

A Promise to You

My promise to you is that if you find a syntax error in my Java code, anywhere in the book, from the preamble onward, and you are the first person to inform me of it, I will write you a check for one hundred American dollars.

And on top of that, I'll add your name in a special thank you section of the next printing of the book, and say all sorts of great things about you. That's how confident I am that there are no code errors in this book.

Your Input is Extremely Important to Me

And to be honest, if there is something in here that's wrong, and you find it, I'll be more than happy to pay. That's my commitment to quality, and to you, the reader. If you can help me improve the quality of this book, I will more than appreciate your help!

Send any errata to: jpaerrata aht cameronmckenzie dawht calm

Here's a little snippet of dialog from the preamble of my Hibernate book that discusses a little bit about what you can expect from my writing style, along with a little bit of editorializing about the things I really hate about too many of the technology books on the market today.

This little diatribe gives you a bit of an idea about what you can expect from my book. Enjoy...

Ooops...Did we miss a step??? Did you just waste an hour???

...Have you ever been working through some code samples in a programming book, and get to some code snippet that, for the life of you, won't compile? You've followed all of the steps, copied the code out line for line, debugged it for three frustrating hours, only to give up, read ahead two pages, and then find out that the authors hadn't told you about a jar file you needed, or the authors introduce a piece of code you needed to write first before the code that wasn't working would ever compile?

I see that all the time, and it annoys the pants off me. And trust me - you don't want to see me without my pants.

Another Promise to You

So, my other promise to you is that if you follow the exercises in this book, as they appear, they will all compile as written. Sure, I think there's a spot in chapter 21 where I write a piece of code on one page that won't compile until you also do the code on the next page, but even then, I have huge boxes warning you that both classes must be written to get things to work. I really try hard to ensure that if you follow the examples, as they are written, everything will compile and run. I want this book to be a fun experience, not an exercise in frustration.

But we'll cover that later...

Oh, and here's another thing I really hate: when technology books introduce a topic, and then say "oh, but we'll cover that later." It's difficult to figure out a good way to teach complex topics like Hibernate, but making a book read like a Visual Basic program that's filled with GOTO statements is not acceptable; It is a disservice to the reader. My personal philosophy is that if you can't take the time to properly explain a given topic, or the reader doesn't have the proper context to fully understand the topic, it shouldn't be brought up at all.

Spaghetti Code and Spaghetti Books: A Disdain for Both

I'm not saying that I'll never, ever, never reference a later section of a book I'm writing, but I really, really, really try not to, and if there's any way to avoid it, I will. I'm not a big fan of GOTO statements, be it in a book or in your VB code...

Okay, that's enough of the diatribe. Now go an purchase this book, either directly from me, or from Amazon.com. It's the best book on Hibernate that's out there.