ORM framework: Reducing the 55% of the developer's persistence (SQL / JDBC)
Cause: Object - Relationship Match (Object) Model VS Relation Model 1 Is the same problem ===, equals () with primary key 4 in the database 4, associated object references, or reference collections with database in foreign bonds, multiplex 5, object navigation object navigation diagram with table connections in the database
Hibernate's fully mapping supports complex object model: combination, inheritance, polymorphism, and "persistent persistence" persistence of transparent, persistent classes do not have to inherit any particular base class or implement any interface efficient access policies (Lazy and instant access) and caching strategies
Hibernate API Introduction Business Layer Related Event Tune Interface: Interceptor Mapping Extensions: UserType, CompositeUsertype, Identifiergenerator, etc.
Persistent layer related basic crud and query: sessionFactory, Session, Transaction, Query Configuration: Configuration
Other J2EE related APIs (may need application server integration) JDBC, JTA, JNDI
Manage the use of non-managed (such as Tomcat) transactions with Hibernate in a non-management environment, and the connection pool is managed by Hibernate (entrusted to apply) Transaction Policy: hibernate.connection.factory_class =
Net.sf.hibernate.Transaction.jdbcTransActionFactory (Direct JDBC transaction)
Management (such as JBoss) container and Hibernate management transaction, connection, security, etc. Transaction strategy: hibernate.connection.factory_class =
Net.sf.hibernate.Transaction.jtatransActionFactory (JTA Support)
JDNI Binding Data Source and Session Factory Hibernate.connection.DataSource = XXXHIBERNATE.SESSION_FACTORY_NAME = XXX
