jBPM Spring Boot嵌入式应用中自定义实体JpaRepository注册失败问题求助

Hey there, let's troubleshoot this issue together! The core error you're hitting is:

Caused by: java.lang.IllegalArgumentException: Not a managed type: class tv.ks.logicservice.entity.ProcessMetaData

This typically means Spring Data JPA/Hibernate can't recognize your ProcessMetaData class as a persistent entity, which is a common gotcha when combining jBPM's auto-configuration with custom Spring Data JPA components.

Let's first recap your code and error details for clarity: #

Error Stacktrace

Caused by: java.lang.IllegalArgumentException: Not a managed type: class tv.ks.logicservice.entity.ProcessMetaData
	at org.hibernate.metamodel.internal.MetamodelImpl.managedType(MetamodelImpl.java:583) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.metamodel.internal.MetamodelImpl.managedType(MetamodelImpl.java:85) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.springframework.data.jpa.repository.support.JpaMetamodelEntityInformation.<init>(JpaMetamodelEntityInformation.java:75) ~[spring-data-jpa-2.5.12.jar:2.5.12]
	at org.springframework.data.jpa.repository.support.JpaEntityInformationSupport.getEntityInformation(JpaEntityInformationSupport.java:66) ~[spring-data-jpa-2.5.12.jar:2.5.12]
	at org.springframework.data.jpa.repository.support.JpaRepositoryFactory.getEntityInformation(JpaRepositoryFactory.java:228) ~[spring-data-jpa-2.5.12.jar:2.5.12]
	at org.springframework.data.jpa.repository.support.JpaRepositoryFactory.getTargetRepository(JpaRepositoryFactory.java:178) ~[spring-data-jpa-2.5.12.jar:2.5.12]
	at org.springframework.data.jpa.repository.support.JpaRepositoryFactory.getTargetRepository(JpaRepositoryFactory.java:161) ~[spring-data-jpa-2.5.12.jar:2.5.12]
	at org.springframework.data.jpa.repository.support.JpaRepositoryFactory.getTargetRepository(JpaRepositoryFactory.java:72) ~[spring-data-jpa-2.5.12.jar:2.5.12]
	at org.springframework.data.repository.core.support.RepositoryFactorySupport.getRepository(RepositoryFactorySupport.java:319) ~[spring-data-commons-2.5.12.jar:2.5.12]
	at org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.lambda$afterPropertiesSet$5(RepositoryFactoryBeanSupport.java:323) ~[spring-data-commons-2.5.12.jar:2.5.12]
	at org.springframework.data.util.Lazy.getNullable(Lazy.java:230) ~[spring-data-commons-2.5.12.jar:2.5.12]
	at org.springframework.data.util.Lazy.get(Lazy.java:114) ~[spring-data-commons-2.5.12.jar:2.5.12]
	at org.springframework.data.repository.core.support.RepositoryFactoryBeanSupport.afterPropertiesSet(RepositoryFactoryBeanSupport.java:329) ~[spring-data-commons-2.5.12.jar:2.5.12]
	at org.springframework.data.jpa.repository.support.JpaRepositoryFactoryBean.afterPropertiesSet(JpaRepositoryFactoryBean.java:144) ~[spring-data-jpa-2.5.12.jar:2.5.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1863) ~[spring-beans-5.3.27.jar:5.3.27]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1800) ~[spring-beans-5.3.27.jar:5.3.27]
... 16 common frames omitted

Your Entity Class

@Entity
@Data
@Table(name = "process_metadata")
public class ProcessMetaData implements Serializable {
    @Id
    @GeneratedValue( strategy = GenerationType.AUTO )
    private Long id;
    
    @Enumerated(EnumType.STRING)
    private EventType eventType;
    
    private String userType;
}

Your Repository Interface

import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.stereotype.Repository;
import tv.ks.logicservice.entity.ProcessMetaData;

@Repository
public interface ProcessMetaDataRepository extends JpaRepository<ProcessMetaData, Long> {
}

Possible Solutions to Fix This #

1. Configure Explicit Package Scanning for JPA
   jBPM's auto-configuration might be overriding or restricting the default package scanning scope for Spring Data JPA. You need to explicitly tell Spring where to look for your entities and repositories:

Add these annotations to your Spring Boot main application class (or a dedicated @Configuration class):

@SpringBootApplication
@EntityScan(basePackages = "tv.ks.logicservice.entity") // Scan your entity package
@EnableJpaRepositories(basePackages = "tv.ks.logicservice") // Adjust if your repos are in a subpackage like "tv.ks.logicservice.repository"
public class YourJbpmApplication {
    public static void main(String[] args) {
        SpringApplication.run(YourJbpmApplication.class, args);
    }
}

2. Verify jBPM and Application Data Source Configuration
   If you've configured a separate data source for jBPM vs. your custom entities, you need to set up multiple EntityManagerFactory beans:

• One for jBPM, pointing to its own entities and tables
• One for your custom entities, with scanning set to your application's packages

But in most cases, the package scanning fix (step 1) should resolve the issue without needing to split data sources.

3. Tweak Your Entity Class (Optional but Good Practice)
   Your entity looks valid, but adding a serialVersionUID to your ProcessMetaData class is a good practice when implementing Serializable:

private static final long serialVersionUID = 1L;

Give these steps a try, starting with step 1—it's the most likely fix for this error! Let me know if you run into any other issues.

内容来源于stack exchange