Hibernate Tutorial

• Introduction to Hibernate Framework
• Hibernate Architecture
• Hibernate Lifecycle
• Difference between JDBC and Hibernate in Java
• JPA vs Hibernate
• Hibernate - Difference Between ORM and JDBC
• Hibernate Example using XML in Eclipse
• Hibernate - Create Hibernate Configuration File with the Help of Plugin

Core Hibernate

• Hibernate - Cache Eviction with Example
• Hibernate - Cache Expiration
• Hibernate - Enable and Implement First and Second Level Cache
• Hibernate - Pagination
• Hibernate - Different Cascade Types
• Hibernate - Caching
• Hibernate - Eager/Lazy Loading
• Hibernate - get() and load() Method
• Hibernate Validator with Example
• Hibernate - Batch Processing
• Hibernate - Interceptors
• Hibernate - Criteria Queries
• Hibernate - Create POJO Classes
• Hibernate - Web Application
• Hibernate - Generator Classes
• Hibernate Example without IDE

Hibernate Mapping

• Hibernate - One-to-One Mapping
• Hibernate - One-to-Many Mapping
• Hibernate - Many-to-One Mapping
• Hibernate - Many-to-Many Mapping
• Hibernate - Component Mapping
• Hibernate - Mapping List
• Hibernate - Collection Mapping
• Hibernate - Bag Mapping
• Hibernate - Difference Between List and Bag Mapping
• Hibernate - SortedSet Mapping
• Hibernate - SortedMap Mapping
• Hibernate - Bidirectional Association
• Hibernate - Lazy Collection

Hibernate Annotations

• Hibernate - Annotations
• Hibernate - @Embeddable and @Embedded Annotation

Hibernate with Spring Framework

• Spring Hibernate Configuration and Create a Table in Database
• Spring ORM Example using Hibernate
• Spring Boot - Validation using Hibernate Validator
• How to Create a Project using Spring MVC and Hibernate 5?
• Spring Boot - Integrating Hibernate and JPA

Hibernate with Database

• Hibernate - Save Image and Other Types of Values to Database
• Hibernate Native SQL Query with Example
• CRUD Operations using Hibernate
• Automatic Table Creation Using Hibernate
• Hibernate - Native SQL
• Hibernate - SQL Dialects
• Hibernate - Query Language
• Hibernate Example using JPA and MySQL

Hibernate Log4j

• Hibernate - Logging by Log4j using xml File
• Hibernate - Logging By Log4j Using Properties File

Inheritance Mapping

• Hibernate - Inheritance Mapping
• Hibernate - Table Per Hierarchy using XML File
• Hibernate - Table Per Hierarchy using Annotation
• Hibernate - Table Per Concrete Class using XML File
• Hibernate - Table Per Concrete Class Using Annotation
• Hibernate - Table Per Subclass Example using XML File
• Hibernate - Table Per Subclass using Annotation

JPA vs Hibernate

Java Persistence API (JPA) and Hibernate are frequently mentioned together and are sometimes used interchangeably, but they aren't the same thing. Both are popular in the Java ecosystem for object-relational mapping (ORM). Let's explore what each of them is and how they differ from each other.

1. Java Persistence API (JPA):

• What is it?

  • JPA is a Java specification for accessing, persisting, and managing data between Java objects and relational databases. It defines a set of concepts and APIs to perform ORM.

• Purpose:

  • To provide a standard API for ORM. Before JPA, ORM tools had their unique ways to define mappings and interact with databases, leading to vendor lock-in.

• Components:

  • It consists of annotations (like @Entity, @Table, @Id) and interfaces (like EntityManager, EntityTransaction).

• Query Language:

  • JPQL (Java Persistence Query Language) is a query language defined by JPA to perform database operations at the object level.

2. Hibernate:

• What is it?

  • Hibernate is an ORM framework that provides an implementation of the JPA specification. However, Hibernate predates JPA and existed as a standalone ORM tool before JPA was introduced.

• Relationship with JPA:

  • Hibernate can function as a standalone ORM tool without JPA. When JPA was introduced, Hibernate adapted and provided an implementation for the JPA specification. Thus, when people say they are using "Hibernate with JPA", they mean they are using Hibernate as the JPA provider.

• Extensions to JPA:

  • Hibernate offers additional features not covered by the JPA specification. Examples include Criteria API, a native SQL query API, and caching mechanisms.

• Query Language:

  • HQL (Hibernate Query Language) and Criteria API were Hibernate's query languages. Once Hibernate started supporting JPA, it also began supporting JPQL.

Comparison: JPA vs Hibernate

1. Nature:

   • JPA: Specification
   • Hibernate: Framework (and also a JPA implementation)

2. Vendor Dependency:

   • JPA: Vendor-independent (there are several JPA providers like Hibernate, EclipseLink, OpenJPA).
   • Hibernate: It's its own vendor but can also act as a JPA provider.

3. Features:

   • JPA: Limited to what the JPA specification defines.
   • Hibernate: Provides all JPA features plus additional features specific to Hibernate.

4. Flexibility:

   • JPA: Using JPA means you aren't tied to a specific provider. You can switch between JPA providers.
   • Hibernate: Using Hibernate-specific features can tie you to Hibernate, making it harder to switch to another JPA provider without refactoring.

5. Complexity:

   • JPA: Easier to learn as it's a subset of what Hibernate offers.
   • Hibernate: Has a steeper learning curve due to its broader set of features.

When to Use Which?

1. Go for JPA when:

   • You want to avoid vendor lock-in.
   • Your requirements are satisfied by the JPA specification, and you don't need advanced features.

2. Opt for Hibernate (with or without JPA) when:

   • You need advanced ORM capabilities beyond JPA.
   • You are already familiar with Hibernate and want to leverage its full power.

Conclusion:

JPA and Hibernate aim to simplify database operations in Java applications by providing ORM capabilities. While JPA provides a standard way to perform ORM, Hibernate offers an implementation of this standard and then some. Understanding the distinction can help in making informed decisions based on the project's needs.