Preface I got into Hibernate because I'm lazy. Specifically, I got tired of writing my own systems to bridge my Java applications and relational databases. I write both Swing and server-based applications; I can't assume (nor do I enjoy) the complexity of EJB container-managed persistence. I hate writing SQL when all I really want to do is write Java code. I really don't like writing endless pages of mindless code, loading my JDBC results into Java objects and back.Simply put, Hibernate solves all of these problems for me, and it does so in a fast, flexible manner. I can use it with Swing, JSP, or as an EJB BMP solution. I can test my code outside of a container. I can even use it to manage my database schema. Regardless of your backgroundwhether you are a nothing-but-JDBC developer or a full EJB-level architectyou can save yourself considerable time and effort by adding Hibernate to your skill set, and in the process you can get a significant leg up on learning EJB 3.0. You can learn the principal terminology and concepts behind EJB 3.0 today, on the Java 2 (JDK 1.4) JVM you are using now. Life is short. Spend less time writing code that bridges your database and your Java application and more time adding new features.
 |
