使用Hibernate 5.4.0.Final时遭遇Unknown entity异常的技术求助

Hey there, let's tackle this frustrating issue you're facing. Upgrading Hibernate from 4.3.5 to 5.4.0 and hitting the Unknown entity: com.mahipal.model.WsdlMst error even after trying standard fixes can be confusing, but there are a few version-specific quirks we can dig into.

First, let's recap what you've already confirmed: your hibernate.cfg.xml correctly includes the <mapping class="com.mahipal.model.WsdlMst"/> entry, and everything works flawlessly in the older version. That tells us the entity itself is valid—so the problem is likely tied to Hibernate 5.x's changes in how it registers entities or builds the SessionFactory.

Here are the most likely fixes to try:

1. Update Your SessionFactory Creation Code #

Hibernate 5.x completely changed how you build a SessionFactory compared to 4.x. If you're still using the old 4.x-style code, it might not properly scan and register your entities.

Old 4.x approach (may fail in 5.x):

SessionFactory sessionFactory = new Configuration().configure().buildSessionFactory();

New 5.x approach (required for proper entity registration):

import org.hibernate.SessionFactory;
import org.hibernate.boot.Metadata;
import org.hibernate.boot.MetadataSources;
import org.hibernate.boot.registry.StandardServiceRegistry;
import org.hibernate.boot.registry.StandardServiceRegistryBuilder;

// Build the service registry first
StandardServiceRegistry registry = new StandardServiceRegistryBuilder()
        .configure("hibernate.cfg.xml") // Loads your config file
        .build();

// Then build metadata and SessionFactory
Metadata metadata = new MetadataSources(registry)
        .getMetadataBuilder()
        .build();

SessionFactory sessionFactory = metadata.buildSessionFactory();

This is the most common culprit when upgrading—Hibernate 5.x relies on MetadataSources and StandardServiceRegistry to properly discover and register entities, whereas the old Configuration method doesn't handle this as reliably in newer versions.

2. Double-Check Entity Class Annotations #

Even though it works in 4.3.5, make sure your WsdlMst class has all required annotations correctly imported:

• Ensure it's annotated with @Entity (from javax.persistence.Entity—Hibernate's specific variant is deprecated in 5.x)
• Verify the @Id annotation is present on your primary field/method and imported from javax.persistence.Id
• Check for typos in the class name or package in both the entity and the hibernate.cfg.xml mapping

Example valid entity structure:

package com.mahipal.model;

import javax.persistence.Entity;
import javax.persistence.Id;

@Entity
public class WsdlMst {
    @Id
    private Long id;
    // Other fields, getters/setters
}

3. Update Your Hibernate Configuration DTD #

Your current config uses the SourceForge DTD URL, which might not resolve properly or have compatibility issues with 5.x. Swap it for the official Hibernate DTD:

<!DOCTYPE hibernate-configuration PUBLIC
        "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
        "http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">

While the 3.0 DTD is still compatible with 5.x, using the official URL ensures proper parsing and avoids potential issues with deprecated links.

4. Clean and Rebuild Your Project #

Sometimes outdated compiled class files or build artifacts can prevent Hibernate from seeing your entity:

• Clean your project's build directory (e.g., target/ or bin/)
• Run a full rebuild with your build tool (Maven/Gradle) to eliminate cached files
• Ensure your entity class is properly packaged in your JAR/WAR file

Give these steps a shot—most likely, updating your SessionFactory creation code to the 5.x style will resolve the unknown entity error. Let me know if any of these work for you!

内容的提问来源于stack exchange，提问作者Mahipal Reddy