Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spring Data JDBC does not consider properly strict configuration mode [DATAJDBC-437] #657

Closed
spring-projects-issues opened this issue Oct 24, 2019 · 0 comments
Assignees
Labels
in: repository type: bug

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Oct 24, 2019

Mark Paluch opened DATAJDBC-437 and commented

Having multiple modules on the classpath (Spring Data JDBC and Spring Data JPA) does not cause Spring Data JDBC back off from repositories that it should not implement. This is, because JdbcRepositoryConfigExtension does not declare identifying repository types and annotations.

We should also aid strict configuration mode detection by introducing spring.factories with an entry for org.springframework.data.repository.core.support.RepositoryFactorySupport.


Affects: 1.1 GA (Moore), 1.0.12 (Lovelace SR12), 2.0 M1 (Neumann)

Reference URL: spring-projects/spring-boot#18721

Issue Links:

  • DATACMNS-1596 Module not exposing any entity identifying annotations claims all repositories

Referenced from: pull request #177

Backported to: 1.1.1 (Moore SR1), 1.0.12 (Lovelace SR12)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: repository type: bug
Projects
None yet
Development

No branches or pull requests

2 participants