Skip to content

Resolution of ambiguous implementations does not work #2487

Closed
@xhaggi

Description

@xhaggi

If you have two or more store-modules e.g. JPA and Elasticsearch in one project and for each of them you have a UserRepository with a custom fragment CustomizedUserRepository and an implementation CustomizedUserRepositoryImpl only one implementation is registered and used for both fragments. No warning or anything else is logged in this case, you just get a QueryCreationException because the wrong implementation is used. Furthermore, a similar case is described in the documentation in the section "Resolution of Ambiguity" [1], but this example no longer works.

@mp911de ping, because you asked me to create an issue for it.

[1] https://docs.spring.io/spring-data/commons/docs/2.5.x/reference/html/#repositories.single-repository-behaviour.ambiguity

Metadata

Metadata

Assignees

Labels

type: regressionA regression from a previous release

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions