processAot fails when ImplicitNamingStrategyComponentPathImpl is used

[coder966]

When there's an entity which has more than one field with the same name, but they are in different embeddable classes, example:

@Entity
@Getter
@Setter
@ToString
public class Example {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    private Personal personal;
    private Business business;

    @Embeddable
    @Getter
    @Setter
    @ToString
    public static class Personal {
        private String address;
    }

    @Embeddable
    @Getter
    @Setter
    @ToString
    public static class Business {
        private String address;
    }

}

the task processAot fails with this error:

Caused by: org.hibernate.MappingException: Column 'address' is duplicated in mapping for entity 'com.example.Example' (use '@Column(insertable=false, updatable=false)' when mapping multiple properties to the same column)

However, this should not happen since

spring.jpa.hibernate.naming.implicit-strategy is set to org.hibernate.boot.model.naming.ImplicitNamingStrategyComponentPathImpl

[philwebb]

Can you please provide a sample that replicates the problem so we can run and debug it.

[coder966]

I made a fresh, minimal reproducer application, please see: https://github.com/coder966/process-aot-bug-48235

[mp911de]

Spring Data JPA AOT processing requires a live EntityManagerFactory for AOT processing. AOT repository generation configures a minimal EntityManagerFactory with the set of known entities to avoid database access during AOT processing. The initial support for AOT repositories does not provide customization hooks for Hibernate settings that would be required to bootstrap the EntityManagerFactory with your entity model.

AOT repositories are enabled by default as of Spring Data JPA 4.0, you have currently two options by setting either configuration property:

// Use the configured EntityManager bean applying all settings, likely to initialize DataSource, useful when providing your own EntityManager bean
spring.aot.jpa.repositories.use-entitymanager=true

// Disable AOT-generated JPA repositories
spring.aot.jpa.repositories.enabled=false

We have to explore whether generally setting ImplicitNamingStrategyComponentPathImpl is a better option than using the default naming strategy.