Hibernate: Difference between revisions
| Line 15: | Line 15: | ||
====Entities vs. value types==== | ====Entities vs. value types==== | ||
Hibernate supports a fine-grained domain model (more classes than tables). An object of '''entity''' type has its own identity (primary key value). An object reference to an entity ist persisted as a reference in the database (a foreign key value). An entity has its own life cylce, it may exist independently of other entities. | Hibernate supports a fine-grained domain model (more classes than tables). An object of '''entity''' type has its own identity (primary key value). An object reference to an entity ist persisted as a reference in the database (a foreign key value). An entity has its own life cylce, it may exist independently of other entities. Criteria for an entity is: | ||
#shared references | |||
#lifecycle dependencies | |||
#identity | |||
====Associations==== | ====Associations==== | ||
Revision as of 14:32, 19 June 2007
Introduction
Hibernate is an open source object/relational mapping tool for Java. Hibernate lets you develop persistent classes following common Java idiom - including association, inheritance, polymorphism, composition and the Java collections framework.

Hibernate makes use of persistent objects commonly called as POJO (POJO = "Plain Old Java Object".) along with XML mapping documents for persisting objects to the database layer. The term POJO refers to a normal Java objects that does not serve any other special role or implement any special interfaces of any of the Java frameworks (EJB, JDBC, DAO, JDO, etc...). Hibernate uses runtime reflection to determine the persistent properties of a class. The objects to be persisted are defined in a mapping document, which serves to describe the persistent fields and associations, as well as any subclasses or proxies of the persistent object. The mapping documents are compiled at application startup time and provide the framework with necessary information for a class. Additionally, they are used in support operations, such as generating the database schema or creating stub Java source files.
Development Process
- copy the following libs to the application lib directory (hibernate core, hibernate annotations, hibernate validation):
ant-antlr-1.6.5.jar
asm-attrs.jar
asm.jar
cglib-2.1.3.jar
commons-collections-2.1.1.jar
commons-logging-1.0.4.jar
dom4j-1.6.1.jar
ejb3-persistence.jar
hibernate-annotations.jar
hibernate-commons-annotations.jar
hibernate-validator.jar
hibernate3.jar
jta.jar
log4j-1.2.11.jar
<JDBCDriver>.jar - create the annotated class e.g. Action.java
- create the Hibernate configuration file hibernate.cfg.xml
- use the persistance classes
Designing the domain model
Entities vs. value types
Hibernate supports a fine-grained domain model (more classes than tables). An object of entity type has its own identity (primary key value). An object reference to an entity ist persisted as a reference in the database (a foreign key value). An entity has its own life cylce, it may exist independently of other entities. Criteria for an entity is:
- shared references
- lifecycle dependencies
- identity
Associations
For a many-end association end the propertie must be of an interface type like java.util.set or java.util.List. Hibernate doesn't manage the associations.
Debugging Concepts
SQL Dump
Add the following entries to hibernate.cfg.xml:
<property name="show_sql">true</property> <property name="format_sql">true</property> <property name="use_sql_comments">true</property>
then all SQL statements are written to stdout.
