Skip to content

Bean-based conditions do not consider factory beans correctly when determining if they are a candidate #42970

Closed
@rajadilipkolli

Description

I have a Spring Boot application that utilizes both Liquibase and Flyway for schema management, connecting to PostgreSQL and MySQL databases. I recently upgraded to Spring Boot 3.4.0-RC1 and it is working as expected with my code.

I have encountered below issue when attempting to simplify the configuration using the new approach as described in documentation.

Cannot resolve reference to bean 'jpaSharedEM_entityManagerFactory' while setting bean property 'entityManager'

Detailed logs can be seen in the github workflow here

Steps to Reproduce :

  1. Download code from the branch qualifier
  2. Bring Postgresql and Mysql database from docker-compose.yml
  3. Application should start succesfully.

Changes made to existing repository can be seen in this PR

 
Expected Behavior:

The application should start successfully using new approach and use Liquibase and Flyway to manage the schema for each database.

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions