JPA Autoconfigure to support ClasspathScanningPersistenceUnitPostProcessor

[XhstormR]

I use spring-boot-starter-data-jpa to configure JPA automatically. I saw ClasspathScanningPersistenceUnitPostProcessor in the reference for spring-data-jpa and I want to use it.

However, I found that using it must be manually configured LocalContainerEntityManagerFactoryBean, and so the automatic configuration of spring-boot-starter-data-jpa will not take effect.

It would be best if the following code configuration worked.

//Kotlin language

@Bean
open fun persistenceUnitPostProcessor(): ClasspathScanningPersistenceUnitPostProcessor {
    val persistenceUnitPostProcessor = ClasspathScanningPersistenceUnitPostProcessor("com.acme.domain")
    persistenceUnitPostProcessor.setMappingFileNamePattern("**/*Mapping.xml")
    return persistenceUnitPostProcessor
}

Sorry for my poor english.

[wilkinsona]

@XhstormR There is nothing poor about your English. Thank you for the suggestion.

Can you please describe in a bit more detail what you want to use ClasspathScanningPersistencveUnitPostProcessor for? It may already be possible to do it:

1. LocalContainerEntityManagerFactoryBean is already auto-configured with the base packages to scan. This can also be controlled using @EntityScan.
2. The spring.jpa.mapping-resources properties may already give you control over the mapping files.

[XhstormR]

@wilkinsona The ORM framework I used earlier is mybatis, which automatically scans XML mapping files under the resources folder.

So I found the ClasspathScanningPersistenceUnitPostProcessor. It can set the Mapping FileNamePattern, but setting it to Bean alone does not work.

I hope spring-boot-starter-data-jpa can do this as well. Like the following example:

mybatis:
├─java
│  └─a
│    └─mapper
│          AddressMapper.java
│          CarMapper.java
│          DriverMapper.java
│
└─resources
    └─mapper
          AddressMapper.xml
          CarMapper.xml
          DriverMapper.xml

spring-boot-starter-data-jpa:
├─kotlin
│   └─a
│        └─entity
│                Account.kt
│                Car.kt
│                Phone.kt
│
└─resources
    │  application.yml
    │
    └─META-INF
            orm.xml
            AccountMapping.xml
            CarMapping.xml
            PhoneMapping.xml

[XhstormR]

@wilkinsona If it cannot, spring.jpa.mapping-resources is also a good choice, at least not requiring the persistence.xml file.

[snicoll]

@XhstormR sorry I don't understand the problem. Spring Boot scans entities and build a persistence.xml for you. If you don't like that, you can define an orm.xml with your configuration or, if necessary, add a spring.jpa.mapping-resources property to get more control over your mapping files.

I don't think there's much else we should do. If you think otherwise, please clarify what the expected behaviour would be.

[XhstormR]

@snicoll I don't want to write SQL in a class, and I don't want to write all the SQL in an orm.xml, but write in multiple files. Each entity class corresponds to a mapping file, for example AccountMapping.xml, CarMapping.xml. The contents of these mapping files are mainly named-query.

I want the mapping file to be automatically scanned, just like the entity class, without needing to specify the file name.

[snicoll]

@XhstormR it looks like that's what the 6 lines of code in your original description is doing, is that correct?