Redeclared reactive delete(Serializable) results in wrong method overload to be invoked eventually [DATACMNS-1023]

[spring-projects-issues]

Mark Paluch opened DATACMNS-1023 and commented

Redeclaring an overloaded method might invoke another existing method because of parameter assignability.

Consider following repository declaration:

interface RxJava2ConvertingRepository extends Repository<Object, Long> {

	Completable delete(Serializable id);
}

backed by a repository ReactiveSortingRepository<Object, Serializable>.

Invoking delete(serializable) may execute delete(Object), declared in the backing repository instead of delete(serializable).

Method selection does not consider direct matches but relies on the order of Class.getMethods to verify parameter assignability

---

Affects: 2.0 M1 (Kay)

Issue Links:

• DATACMNS-943 Redeclared save(Iterable) results in wrong method overload to be invoked eventually

• DATACMNS-988 Provide RxJava 2 Repository interfaces

Referenced from: commits c247ee9, d87cb03, e737103