如何将外部Jar包中的@Entity类加载为Spring托管类型？

项目结构：

• 核心Spring应用：集成基础API
• 插件：基于上述API构建，独立编译后存放于核心应用运行目录的plugins文件夹中，包含继承自API父类的@Entity注解类
• 核心应用已通过自定义ClassLoader和ClassLoaderManager成功加载插件内所有类，但Spring无法识别这些插件中的@Entity类为JPA托管类型

已尝试的失败方案 #

曾通过自定义PersistenceUnitPostProcessor扩展ClasspathScanningPersistenceUnitPostProcessor，尝试将插件Jar包URL添加到持久化单元信息中，代码如下：

@Bean
public LocalContainerEntityManagerFactoryBean entityManagerFactory(DataSource dataSource) {
    LocalContainerEntityManagerFactoryBean bean = new  LocalContainerEntityManagerFactoryBean();
    bean.setDataSource(dataSource);
    bean.setPackagesToScan(// 注入扫描包路径);
    bean.setJpaVendorAdapter(new HibernateJpaVendorAdapter());
    CustomUnitPostProcessor postProcessor = new CustomPostProcessor("基础包路径");
    bean.setPersistenceUnitPostProcessors(postProcessor);
    return bean;
}

public class CustomUnitPostProcessor extends ClasspathScanningPersistenceUnitPostProcessor {

    public CustomUnitPostProcessor(String basePackage) {
        super(basePackage);
    }

    @Override
    public void postProcessPersistenceUnitInfo(MutablePersistenceUnitInfo pui) {
        // 通过pui.addJarFileURL()添加Jar包URL
        super.postProcessPersistenceUnitInfo(pui);
    }
}

执行时抛出org.hibernate.boot.registry.classloading.spi.ClassLoadingException: Unable to load class [目标实体类名]异常，导致EntityManagerFactory初始化失败。

可行解决方案 #

方案一：修正自定义PersistenceUnitPostProcessor，指定插件类加载器 #

问题根源在于Hibernate默认使用系统类加载器，无法访问插件类。需确保持久化单元使用自定义的插件类加载器：

@Bean
public LocalContainerEntityManagerFactoryBean entityManagerFactory(DataSource dataSource, ClassLoaderManager classLoaderManager) {
    LocalContainerEntityManagerFactoryBean bean = new LocalContainerEntityManagerFactoryBean();
    bean.setDataSource(dataSource);
    // 配置核心应用的实体扫描包
    bean.setPackagesToScan("com.core.entity");
    bean.setJpaVendorAdapter(new HibernateJpaVendorAdapter());
    
    // 传入插件基础包和自定义类加载器
    CustomUnitPostProcessor postProcessor = new CustomUnitPostProcessor("com.plugin.entity", classLoaderManager.getPluginClassLoader());
    bean.setPersistenceUnitPostProcessors(postProcessor);
    return bean;
}

public class CustomUnitPostProcessor extends ClasspathScanningPersistenceUnitPostProcessor {
    private final ClassLoader pluginClassLoader;

    public CustomUnitPostProcessor(String basePackage, ClassLoader pluginClassLoader) {
        super(basePackage);
        this.pluginClassLoader = pluginClassLoader;
        // 设置扫描时使用插件类加载器
        setBeanClassLoader(pluginClassLoader);
    }

    @Override
    public void postProcessPersistenceUnitInfo(MutablePersistenceUnitInfo pui) {
        // 先将持久化单元的类加载器设置为插件类加载器
        pui.setClassLoader(pluginClassLoader);
        
        // 遍历plugins目录下的所有Jar包并添加到持久化单元
        try {
            File pluginsDir = new File("plugins");
            for (File jarFile : pluginsDir.listFiles((dir, name) -> name.endsWith(".jar"))) {
                pui.addJarFileURL(jarFile.toURI().toURL());
            }
        } catch (IOException e) {
            throw new RuntimeException("添加插件Jar包到持久化单元失败", e);
        }
        
        super.postProcessPersistenceUnitInfo(pui);
    }
}

核心改动：给MutablePersistenceUnitInfo设置插件类加载器，同时让扫描器使用该类加载器，确保Hibernate能正确加载插件中的实体类。

方案二：直接指定JPA托管类型，跳过包扫描 #

如果包扫描机制无法适配自定义类加载器，可直接收集已加载的插件实体类，手动注册为托管类型：

@Bean
public LocalContainerEntityManagerFactoryBean entityManagerFactory(DataSource dataSource, ClassLoaderManager classLoaderManager) {
    LocalContainerEntityManagerFactoryBean bean = new LocalContainerEntityManagerFactoryBean();
    bean.setDataSource(dataSource);
    // 配置核心应用的实体扫描包
    bean.setPackagesToScan("com.core.entity");
    bean.setJpaVendorAdapter(new HibernateJpaVendorAdapter());

    // 收集所有已加载的插件中带@Entity注解的类
    Set<Class<?>> managedTypes = new HashSet<>();
    for (Class<?> clazz : classLoaderManager.getLoadedPluginClasses()) {
        if (clazz.isAnnotationPresent(Entity.class)) {
            managedTypes.add(clazz);
        }
    }
    
    // 设置JPA托管类型
    bean.setManagedTypes(managedTypes);

    return bean;
}

该方案依赖ClassLoaderManager能提供所有已加载的插件类，直接筛选实体类注册，避免类加载器适配问题。

方案三：给Hibernate指定自定义类加载器 #

在JPA配置属性中直接指定Hibernate使用插件类加载器，从根源解决类加载问题：

@Bean
public LocalContainerEntityManagerFactoryBean entityManagerFactory(DataSource dataSource, ClassLoaderManager classLoaderManager) {
    LocalContainerEntityManagerFactoryBean bean = new LocalContainerEntityManagerFactoryBean();
    bean.setDataSource(dataSource);
    bean.setPackagesToScan("com.core.entity", "com.plugin.entity");
    bean.setJpaVendorAdapter(new HibernateJpaVendorAdapter());

    // 添加Hibernate类加载器配置
    Properties jpaProperties = new Properties();
    jpaProperties.put("hibernate.classLoader.application", classLoaderManager.getPluginClassLoader());
    bean.setJpaProperties(jpaProperties);

    return bean;
}

此方式让Hibernate全程使用插件类加载器加载相关类，无需额外处理包扫描逻辑。

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